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.65221 npmAGPL 3.0
- FlicenseCqualityBmaintenanceEnables 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.86-

io.github.zkp2p/peerofficial
AlicenseNot gradedqualityAmaintenanceExposes 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.43 npmMIT- -licenseNot gradedqualityNot gradedmaintenanceEnables an MCP host to inspect and operate a Shopware 6 shop through the Admin API: products, orders, customers, documents, stock, sales channels and trading settings, plus a one-call health audit, anomaly pulse, sales and customer reports, stock forecasting, and simulation of the customer checkout to explain cart errors. Read-only by default, with guarded writes that show a dry run first.-
- AlicenseNot gradedqualityBmaintenanceLets AI agents search merchant product catalogs, obtain signed offers with agent pricing, and run checkout sessions that always settle on the merchant's own payment page. It also scores any website's agent-readiness and exposes the published rubric checks.MIT
- AlicenseNot gradedqualityBmaintenancePublishes a read-only data handle exposing SQL querying and URL fetching, plus a separately scoped read-write handle for actions like issuing refunds and sending customer email. Every call is checked against a permission set frozen before any untrusted text is read, with irreversible actions held behind one or two human approval signatures.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.