gumroad-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GUMROAD_ACCESS_TOKEN | Yes | Access token from Gumroad settings (Settings → Advanced → Applications → create app → copy access token). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List all products in the store: name, permalink, price, published state, and sales count. Answers 'what am I actually selling right now?' |
| salesA | List sales, fully paginated. Dates are YYYY-MM-DD (after defaults to today — pass e.g. after='2026-01-01' for history). Returns per-sale price, product, email domain (full buyer email withheld), refund state, and totals. |
| revenue_summaryA | One-call store health check: product count, published count, lifetime
sales counts per product, and revenue since |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.