Skip to main content
Glama
gumroad-mcp

gumroad-mcp

gumroad-mcp

Read-only MCP server for your Gumroad store — products, sales, and revenue summaries, exposed as tools your AI agent can call.

Built by a store operator, not from the API docs alone:

  • Sales are fully paginated — and say so when they aren't. The v2 sales endpoint pages by page_key; naive clients read page 1 and silently under-report. This server walks every page. There is a hard page cap so a huge store can't hang a session, and if that cap is ever hit the response carries "complete": false plus an explicit warning that the totals are a floor. A truncated total is never returned as if it were the real number.

  • Money is integer cents + a formatted string. Models shouldn't do float arithmetic on revenue.

  • Refunds are first-class. sales and revenue_summary report gross and net-of-refunds.

  • Buyer privacy by default. Sales rows expose the buyer's email domain only — enough for channel analysis, no PII handed to the model.

  • Read-only by design. Only GET endpoints. The token comes from the environment and is never echoed or logged.

  • No false delivery alarms. Gumroad returns an empty file_info for multi-file products, so "empty" does not mean "no file attached". This server reports that field as the raw API fact it is (file_info_reported_by_api) and attaches a note, instead of asserting a delivery status the endpoint cannot actually tell you.

Requires the 1.x MCP SDK. mcp 2.0.0 removed mcp.server.fastmcp, so the dependency is pinned mcp>=1.0.0,<2.0.0. Porting to the 2.x (mcp.server.mcpserver) API is tracked as follow-up.

Tools

Tool

What it answers

list_products()

What am I actually selling? Name, permalink, price, published state, sales count

sales(after, before, product_id)

Every sale in a window, paginated to the end, with totals

revenue_summary(after)

One-call health check: product counts, lifetime sales per product, revenue since a date (default: this month)

Related MCP server: Shopify MCP

Install

git clone https://github.com/stcmain/gumroad-mcp.git
cd gumroad-mcp
pip install .

Get a token: Gumroad → Settings → Advanced → Applications → create app → copy the access token.

Register with Claude Code:

claude mcp add --scope user gumroad --env GUMROAD_ACCESS_TOKEN=your_token -- gumroad-mcp

Or any MCP client config:

{
  "mcpServers": {
    "gumroad": {
      "command": "gumroad-mcp",
      "env": { "GUMROAD_ACCESS_TOKEN": "your_token" }
    }
  }
}

License

MIT © Zachary Pampu

Available Tools

3 tools
list_productsA

List all products in the store: name, permalink, price, published state, and sales count. Answers 'what am I actually selling right now?'

Inputs: no named parameters. Returns: result

revenue_summaryA

One-call store health check: product count, published count, lifetime sales counts per product, and revenue since after (YYYY-MM-DD, default: start of current month). The number an operator actually wants first.

Inputs: after. Returns: result

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.

Inputs: after, before, product_id. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    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 Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server implementation for Gumroad, enabling MCP-compatible AI clients like Claude Desktop to interact with Gumroad API.
      11
      216 npm
      32
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      6
      30 PyPI
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that integrates with Gumroad API, enabling Claude to list products, view sales, and get sales summaries for your Gumroad store.
      4
      216 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A 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.
      15
      10 npm
      Apache 2.0