Mcp Server Gelato

Created By
madzarm9 months ago
Server for managing your Gelato POD account.
Overview

What is Mcp Server Gelato?

Mcp Server Gelato is a server designed for managing Gelato POD (Print-On-Demand) accounts, providing integration with Gelato's API for order management and product catalog exploration.

How to use Mcp Server Gelato?

To use the server, install it via Python package management tools like pip or uv, configure it with your Gelato API key, and run the server to access its features.

Key features of Mcp Server Gelato?

  • Advanced order search with multiple filters (status, country, date range, etc.)
  • Retrieve specific order details and summaries
  • Explore product catalogs with filtering capabilities
  • Check stock availability and shipment methods
  • Comprehensive error handling and async support for better performance

Use cases of Mcp Server Gelato?

  1. Managing and tracking print-on-demand orders efficiently.
  2. Searching and retrieving product information from Gelato's catalogs.
  3. Integrating with e-commerce platforms for seamless order processing.

FAQ from Mcp Server Gelato?

  • What is required to run the server?

You need Python 3.13+ and a valid Gelato API key.

  • Is there a graphical interface?

No, it is a command-line tool designed for developers.

  • Can I customize the server?

Yes, you can extend its functionality by adding new tools and resources.

Project Info
Created At
9 months ago
Updated At
6 months ago
Author Name
madzarm
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago