Gumroad MCP Server
Related Servers
Alternatives to Gumroad MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to perform commerce and license operations—such as orders, subscriptions, refunds, checkouts, invoices, and webhooks—through shared MCP/CLI tasks with private profiles, explicit confirmations, reviewed batches, and bounded exports.6516 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to read from a real order and inventory database while routing every destructive write — cancellations, refunds, stock adjustments — into a pending-actions queue that a human approves or rejects in a dashboard. Includes scoped permissions, rate limiting, idempotency, and an append-only audit log so agent activity stays bounded and attributable.MIT
- AlicenseCqualityBmaintenanceEnables AI agents and CLI users to perform confirmed shop operations, manage products, orders, collections, webhooks, and promotions, and handle bounded metadata exports and private uploads through a local stdio server.8613 npmAGPL 3.0

io.github.zkp2p/peerofficial
AlicenseNot gradedqualityBmaintenanceExposes protocol, indexer, market, checkout, and cash-flow operations to agents through read-only, cash-preparation, and full operator profiles, with state-changing actions previewed before execution unless explicitly authorized.47 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up customers, orders, products, and stock; take role-restricted actions such as creating orders and handling refunds; enforce business rules; and maintain a tamper-evident audit log.MIT
- AlicenseNot gradedqualityBmaintenanceEnables read- or write-scoped access to synthetic enterprise orders, inventory, support tickets, and metrics via schema-validated JSON-RPC tools over stdio and HTTP, with permission allow-lists and audit logging. It also exposes enterprise resources and prompt templates for grounded, cited, multi-step assistant workflows.MIT
TDQS
Scored across 57 tools
Tools are well-differentiated by resource and action (e.g., list_products vs get_product, create_variant vs update_variant). A few potential overlaps exist, such as enable_product/disable_product vs update_product, and increment_license_uses vs decrement_license_uses, but descriptions clarify scope. The local meta-tools (preview_commerce_batch, submit_commerce_batch, export_resources) are distinct from native API tools.
All tool names follow a consistent verb_noun pattern (list_products, create_product, get_sale, etc.), with no mixing of camelCase or other styles. Even special tools like preview_commerce_batch and submit_commerce_batch fit the pattern. This makes the set highly predictable.
With 57 tools, the server is heavily over-provisioned for typical agent use. While each tool may earn its place individually, the sheer number increases selection complexity and cognitive load. A smaller, more focused set would likely suffice for most workflows.
The tool set provides comprehensive CRUD and lifecycle coverage across all major Gumroad resources: products, sales, licenses, variants, offer codes, custom fields, payouts, subscriptions, and account settings. Even edge cases like license rotation and refund policy updates are included. No obvious gaps remain.