stripe-analytics-mcp
Related Servers
Alternatives to stripe-analytics-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables querying MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy directly inside Claude, allowing natural language questions about business metrics.520 npmMIT
- AlicenseAqualityBmaintenanceMCP server that gives AI assistants real-time access to Stripe business metrics like MRR, churn, and revenue forecasts via natural language queries.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI-powered analytics from Stripe, PayPal, and Google Analytics 4 (BigQuery) data sources with built-in guardrails and automated workflows for financial and web performance insights.-

Kordi MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceTrack, analyze, and act on your streaming & SaaS subscriptions from any AI agent.MIT- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Stripe accounts to query customers, revenue, invoices, subscriptions, disputes, and issue refunds.36 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents access to RevenueCat's Charts & Metrics API. Query MRR, churn, trial conversion, revenue, and 17 more subscription metrics directly from Claude, Cursor, or any MCP client.55 npmMIT
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.