stripe-ops-mcp
Related Servers
Alternatives to stripe-ops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude and other MCP clients to query Stripe receivables, payouts, disputes, balance, approved supplier bills, and cash forecasts in plain English through read-only finance tools.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to safely inspect Stripe billing data such as subscriptions, invoices, failed payments, and churn, with read-only access, per-tool permissions, and a tamper-evident audit log.8 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude to query Stripe data—customers, charges, subscriptions, invoices, balance, events, and more—through 17 read-oriented tools, with optional write protections and a read-only default for remote deployments.-
- AlicenseNot gradedqualityFmaintenanceRead-only Stripe finance, ops, and risk reporting exposed via MCP, HTTP API, and CLI. Enables querying balances, payments, customers, payouts, reconciliation, and risk alerts without mutating Stripe state.MIT
- AlicenseAqualityBmaintenanceEnables an MCP client to answer revenue questions about a Stripe account — normalized MRR/ARR, subscription and customer churn, failed payments and a one-call revenue summary, all grouped per currency. Access is read-only and a built-in deterministic demo dataset lets every tool be tried without a Stripe API key.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables integration with Stripe APIs through function calling, supporting operations on customers, products, invoices, subscriptions, and more.25,970 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing charges, detecting duplicates, summarizing revenue, and fetching customer profiles. No overlap in functionality; an agent can easily select the right tool for the job.
All names use snake_case and are descriptive, but three follow a verb_noun pattern (list_, find_, get_) while revenue_summary is a noun-only phrase. Minor inconsistency, yet still predictable and readable.
Four tools is slightly on the lower side, but the set is tightly scoped to stripe operations monitoring. The count feels acceptable rather than overly thin for a focused utility.
The tools cover only read/analytics operations: listing charges, detecting duplicates, revenue summaries, and customer lookup. Missing obvious operational capabilities like creating refunds, retrieving charge details, or managing customers/subscriptions, leaving significant gaps for real-world ops.