Revenue Mcp

io.github.warfare-hubPublished by GitHub account warfare-hubv0.1.2Updated Oct 24, 2026

Query MRR, churn, and revenue from Stripe, Gumroad & Lemon Squeezy in Claude

VerifiedSTDIODesktop onlyFinanceData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant query MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy inside a chat.

What you can do
Provides tools that pull subscription revenue metrics from connected payment platforms. Tools include get_revenue_summary (MRR, ARR, new MRR, churn across platforms), get_mrr_by_platform, get_product_breakdown (revenue and subscribers per product, Stripe), get_recent_revenue (total over the last N days), and get_churn_summary (churn MRR, new MRR, net new MRR, churn rate). Coverage varies by platform: Stripe supports MRR, churn, product breakdown, and recent revenue; Gumroad supports product breakdown and recent revenue; Lemon Squeezy supports MRR and recent revenue.
When to use it
Useful for founders or operators who want to ask revenue questions in natural language without opening each payment dashboard. Best when revenue lives on Stripe, Gumroad, or Lemon Squeezy and you want quick MRR, churn, or product-level answers in context.
Requirements
Runs locally as an npm package (npx revenue-mcp) over stdio, configured in Claude Desktop. Requires API credentials supplied as environment variables: STRIPE_SECRET_KEY, GUMROAD_ACCESS_TOKEN, and LEMONSQUEEZY_API_KEY. Network access to the payment providers is needed. Desktop only; no web executable.
Before you install
The server asks for live payment-platform secrets: STRIPE_SECRET_KEY (which may be a live key), GUMROAD_ACCESS_TOKEN, and LEMONSQUEEZY_API_KEY. These grant broad read access to financial data, so store them carefully and prefer test keys where possible. The tools are described as read-only queries, but the credentials themselves are sensitive and should not be shared or committed.

Installation

In SourceWeft

  1. Open Revenue Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Revenue MCP

Query your MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy directly inside Claude.

No more switching tabs. Ask Claude "what's my MRR this month?" and get the answer in context.

Supported Platforms

PlatformMRRChurnProduct BreakdownRecent Revenue
Stripe✅✅✅✅
Gumroad——✅✅
Lemon Squeezy✅——✅
Paddle🔜🔜🔜🔜
Polar🔜🔜🔜🔜

Quick Start

1. Get your API keys

  • Stripe: Dashboard → Developers → API keys → Secret key
  • Gumroad: Settings → Advanced → Applications → Generate access token
  • Lemon Squeezy: Settings → API → Create key

2. Add to Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "revenue-mcp": {      "command": "npx",      "args": ["-y", "revenue-mcp"],      "env": {        "STRIPE_SECRET_KEY": "sk_live_...",        "GUMROAD_ACCESS_TOKEN": "your_token",        "LEMONSQUEEZY_API_KEY": "your_key"      }    }  }}

Restart Claude Desktop. Done.

3. Ask Claude anything

  • "What's my MRR this month?"
  • "How much did I make in the last 30 days?"
  • "Which product is generating the most revenue?"
  • "What's my churn rate?"
  • "Break down my revenue by platform"

Tools

ToolDescription
get_revenue_summaryFull summary across all platforms — MRR, ARR, new MRR, churn
get_mrr_by_platformMRR comparison table across platforms
get_product_breakdownRevenue + subscribers per product (Stripe)
get_recent_revenueTotal revenue over last N days
get_churn_summaryChurn MRR, new MRR, net new MRR, churn rate

License

MIT

Source: README.md at commit 51e714e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.