Stripe MCP

Stripe provides APIs for payments, subscriptions, invoices, marketplaces, and revenue systems. Its homepage reports 135+ currencies and payment methods, $1.9 trillion processed in 2025, 200 million active subscriptions, and 99.999% historical service uptime. The official MCP server exposes selected operations to compatible assistants. Financial consequences make permissions more important than convenience.

Pricing and economics

Standard US online cards cost 2.9% plus 30¢ per successful domestic transaction; custom pricing requires sales contact. On $5, the fee is 44.5¢ or 8.9%; on $100, it is $3.20 or 3.2%. Verify international, conversion, dispute, Billing, Connect, Tax, Radar, Terminal, and payout fees. The pricing page references 125+ payment methods, but rates vary by product and country.

Customers, products, prices, subscriptions, invoices, refunds, and webhooks share a coherent API model. Test mode avoids moving money, while idempotency keys reduce duplicate operations. Compare Stripe, subscription manager Chargebee, and orchestration via n8n or Zapier.

Honest assessment

API maturity, test mode, and public transaction pricing are strengths. The weakness is consequence: a wrong refund or subscription change loses money or harms a customer. MCP may not cover every dashboard task, and models can choose the wrong operation. Follow agent security practices: read-only first, isolated test/live authorization, confirmation for mutations, amount thresholds, and tool-call logs. Test 30 scenarios including declines, duplicate webhooks, refunds, disputes, failed invoices, upgrades, cancellation, and unauthorized requests. Measure wrong-resource selection, duplicates, latency, and review time. Model fees using actual transaction sizes and international mix.

Practical evaluation

Run a two-week pilot on one bounded workflow before granting broad access. Use at least 30 representative tasks, including invalid input, permission failures, stale records, provider timeouts, and recovery cases. Record completion rate, factual or technical correctness, p50 and p95 latency, human review minutes, and total cost per accepted result. Start with read-only scopes and a test workspace where possible. Inspect the exact tools exposed to an agent, then add write access only after an owner defines approval, audit, and rollback procedures. Confirm retention, regional processing, subprocessors, data export, rate limits, support terms, and whether customer content is used for model training.

Build an annual cost model from real volume. Include subscriptions, metered usage, implementation, identity administration, monitoring, reviewer labor, and incident response. Add a 25% volume buffer and test cancellation or export before committing. A purchase is justified when the measured time and risk reduction exceed those costs; a polished demo alone is not evidence of production value.

The current MCP documentation adds important controls beyond the underlying API. Interactive clients can use OAuth, autonomous applications can use permission-scoped Agent Keys, and administrators can revoke sessions or disable MCP access for a team. Stripe states that after October 31, 2026 the server will reject full-access secret keys and restricted keys without the Agent tag. Sensitive write actions such as refunds and outbound payments can require human confirmation, with approvals expiring after 24 hours. These controls reduce risk, but teams should still begin in a sandbox with read-only access and inspect MCP tool-call logs in Workbench.