stripe-analytics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRIPE_SECRET_KEY | Yes | Stripe secret key (sk_test_... or sk_live_...). Read-only access is sufficient. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mrrA | Compute current Monthly Recurring Revenue (MRR) from active Stripe subscriptions. Normalizes annual/weekly/daily subscriptions to monthly amounts, applies discounts, and excludes trials. Returns total MRR, subscription count, and status breakdown. |
| get_churnB | Compute customer churn rate and revenue churn rate for a given period. Returns percentage of customers lost, percentage of revenue lost, counts of churned customers, and churned MRR amount. |
| get_revenue_by_planA | Break down MRR by pricing plan/product. Returns a table showing each plan with subscriber count, MRR contribution, and percentage of total revenue. |
| get_subscriber_statsB | Get subscriber statistics for a given period. Returns total active subscribers, new subscribers, churned subscribers, net change, trial count, and past due count. |
| get_recent_changesB | List recent subscription changes including new subscriptions, cancellations, upgrades, downgrades, and failed payments. Returns detailed event list with customer info and summary counts. |
| get_dashboardA | The morning check — get everything important in one call. Returns: current MRR with week-over-week change, MRR movement breakdown (new/expansion/contraction/churn), failed payments needing attention, trials expiring in 3 days, and Quick Ratio. Use this when someone asks "how's my business doing?" or "morning check" or "what happened overnight?" |
| get_failed_paymentsA | Get all failed payment attempts with customer email, amount, failure reason, attempt count, and plan. These are recoverable revenue — money you can get back by reaching out to customers. Shows total revenue at risk. |
| get_mrr_movementA | MRR waterfall showing how MRR changed over a period: new MRR from new customers, expansion from upgrades, contraction from downgrades, and churn from cancellations. Answers "how did my MRR change this week/month?" |
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 8 tools
Each tool targets a distinct analytics concept (MRR, churn, revenue by plan, subscriber stats, recent changes, dashboard, failed payments, MRR movement). However, churn-related data appears in get_churn, get_subscriber_stats, get_recent_changes, and get_mrr_movement, and get_dashboard overlaps with several individual tools, creating mild misselection risk.
All tools use a consistent snake_case verb_noun pattern (get_mrr, get_churn, etc.), making the naming predictable and easy to parse.
Eight tools is well-scoped for a Stripe analytics server, covering essential metrics without redundancy or excessive fragmentation.
The surface covers core analytics (MRR, churn, plans, subscribers, changes, failed payments, movement, dashboard). Minor gaps exist for deeper customer-level or cohort analysis, but agents can work around them with existing tools.