gumroad-mcp
Related Servers
Alternatives to gumroad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that integrates with Gumroad API, enabling Claude to list products, view sales, and get sales summaries for your Gumroad store.477 npmMIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server implementation for Gumroad, enabling MCP-compatible AI clients like Claude Desktop to interact with Gumroad API.1177 npm32MIT
- AlicenseAqualityAmaintenanceA read-only MCP server that exposes the full Shopify Admin GraphQL API through 6 universal tools, with multi-store support and mutation rejection at the parser level for safety.6MIT
- FlicenseAqualityCmaintenanceA local MCP server that enables querying Amazon Selling Partner API for profitability analysis (revenue, fees, COGS, net margin) and inventory alerts (FBA stock levels and low-stock warnings) using read-only operations.9-
- AlicenseAqualityCmaintenanceA local-first, read-only MCP server for the Loyverse POS API that lets AI assistants query receipts, items, employees, customers, stores, and sales analytics — built for secure local use with Personal Access Tokens.156 npmApache 2.0
- AlicenseBqualityCmaintenanceA read-only MCP server for SimpleShop accounting data, enabling AI agents to find documents, download PDFs, inspect products, and review sales exports.5MIT
TDQS
Scored across 3 tools
Tools are mostly distinct: list_products focuses on the product catalog, sales provides transaction-level details, and revenue_summary gives aggregate metrics. There is minor overlap in sales counts per product between list_products and revenue_summary, but descriptions clarify their different intents.
Naming is mixed: list_products follows verb_noun, while sales and revenue_summary are plain nouns. All are lowercase snake_case, but the lack of a consistent verb_prefix pattern makes it slightly less predictable.
Three tools is a tight, well-scoped set for a read-only store analytics server. Each tool covers a distinct high-level need (catalog, transactions, summary) without unnecessary bloat or missing core functions.
For the apparent purpose of store health monitoring, the surface is fairly complete: product listings, detailed sales history, and revenue summaries are all covered. A minor gap is the lack of a single-product detail or sales-by-sale retrieval, but pagination and filtering mitigate this.