Stripe analytics — revenue, customers, subscriptions, refunds, churn from Claude.
Stripe analytics — revenue, customers, subscriptions, refunds, churn from Claude. That is what the stripe mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Connect Claude to your Stripe dashboard. Revenue, customers, subscriptions -- all from chat.
The server publishes 8 tools. What each one is for:
get_revenue_summary — Get gross revenue, fees, net revenue, and transaction count for a periodget_customer_count — The get_customer_count tool exposed by this serverget_subscription_metrics — Breakdown of subscription statuses: active, trialing, past_due, canceledget_top_customers — The get_top_customers tool exposed by this serverget_recent_charges — The get_recent_charges tool exposed by this serverget_refund_summary — The get_refund_summary tool exposed by this serverget_product_revenue — The get_product_revenue tool exposed by this serverget_mrr — Monthly Recurring Revenue calculated from all active subscriptionsSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: STRIPE_SECRET_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Stripe's toolset — get_revenue_summary, get_customer_count, get_subscription_metrics and 5 more — is a fair guide to whether it matches your workflow. It is maintained by lordbasilaiassistant-sudo; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_revenue_summary | Get gross revenue, fees, net revenue, and transaction count for a period. |
| get_customer_count | The get_customer_count tool exposed by this server. |
| get_subscription_metrics | Breakdown of subscription statuses: active, trialing, past_due, canceled. |
| get_top_customers | The get_top_customers tool exposed by this server. |
| get_recent_charges | The get_recent_charges tool exposed by this server. |
| get_refund_summary | The get_refund_summary tool exposed by this server. |
| get_product_revenue | The get_product_revenue tool exposed by this server. |
| get_mrr | Monthly Recurring Revenue calculated from all active subscriptions. |
{
"mcpServers": {
"stripe-analytics": {
"command": "npx",
"args": ["-y", "mcp-stripe-analytics"],
"env": {
"STRIPE_SECRET_KEY": "sk_live_..."
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| STRIPE_SECRET_KEY | Credential the server authenticates with. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.