Stripe MCP
Work with Stripe customers, products, payments, and related account resources.
Verdict
Common use cases
- Pull monthly recurring revenue during budget reviews
- Check failed payment counts before customer calls
- Generate invoice summaries for quarterly reports
- List active subscriptions by plan tier
- Verify refund status during support escalations
Integration
- Vendor
- Stripe MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
stripe_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCP Servers. 2. Search for 'Stripe MCP' and click Connect. 3. You'll redirect to Stripe's OAuth consent screen — log in with an account that has API access (typically an admin or developer role). 4. Stripe will ask you to authorize access to customers, invoices, payment intents, subscriptions, and balance data — approve all requested scopes. 5. After redirect back to Switchy, you'll see 'Stripe MCP connected' with a green indicator. 6. Create or open a Project, type '@Stripe' in the chat, and ask 'show me total revenue for the last 30 days' to confirm the connection works. 7. If the MCP returns data, you're ready — if it errors, revisit Settings > Integrations and check that your Stripe account has live API keys enabled (test mode won't surface real transactions).
What teammates see: by default, memories from Stripe MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Revenue This Quarter
@Stripe show me total revenue from successful charges in Q1 2025, broken down by week.
Failed Payments Report
@Stripe list all failed payment attempts in the past 7 days with customer email and failure reason.
Active Subscription Count
@Stripe how many active subscriptions do we have right now, grouped by plan name?
Draft Invoice for Customer
@Stripe create a draft invoice for customer ID cus_abc123 with a $500 line item for consulting services.
Recent Refund Summary
@Stripe show me all refunds issued in the last 30 days with amounts and reasons.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@stripe show me the last 10 successful payments from the past week, grouped by customer
Here's a summary of your recent successful payments: Customer A (cus_abc123): 3 payments totaling $847.50 - $299.00 on Jan 15 (inv_001) - $348.50 on Jan 16 (inv_002) - $200.00 on Jan 18 (inv_003) Customer B (cus_def456): 2 payments totaling $1,200.00 - $600.00 on Jan 14 (inv_004) - $600.00 on Jan 17 (inv_005) [5 more customers listed] All payments processed via card. No disputes or refunds in this period.
This read-only query requires OAuth scope for viewing payment data. Response format depends on your Stripe account's payment volume — high-traffic accounts may need date-range narrowing to avoid timeouts. The MCP returns structured data the AI can reformat; exact field availability varies by your Stripe API version.
@stripe create a $150 invoice for customer cus_xyz789 with line item 'Q1 Consulting - 3 hours' due in 14 days
Invoice created successfully: Invoice ID: in_1AbCdEfGhIjKlMnO Customer: cus_xyz789 (jane@example.com) Amount: $150.00 USD Line item: Q1 Consulting - 3 hours ($150.00) Due date: January 31, 2025 Status: Draft The invoice is in draft status. You can review it in your Stripe dashboard before sending. Would you like me to finalize and send it now?
This write operation requires OAuth scope for invoice creation. The MCP creates the invoice but leaves it in draft state by default — you must explicitly confirm sending to avoid accidental billing. Customer ID must exist in your Stripe account; the MCP won't validate email addresses or create new customers automatically.
@stripe pull all failed payment attempts from the last 30 days and draft an email to our finance team summarizing the top 3 failure reasons
I found 47 failed payment attempts in the past 30 days. Here's a draft email: --- Subject: Payment Failure Summary - Last 30 Days Team, We've seen 47 failed payments totaling $8,340 in attempted charges. Top failure reasons: 1. **Insufficient funds (19 failures, $3,200)** — mostly on the 1st and 15th, suggesting payroll timing issues. 2. **Expired cards (14 failures, $2,900)** — 8 customers haven't updated payment methods in 6+ months. 3. **Card declined by issuer (10 failures, $1,800)** — no clear pattern; may need manual outreach. Recommend: automated email campaign for expired cards, consider shifting billing dates for insufficient-funds cohort. ---
This synthesis example combines Stripe data retrieval with AI reasoning. The MCP fetches raw failure events; the AI interprets patterns and drafts communication. Accuracy depends on your Stripe account's metadata completeness — if failure codes aren't standardized, the AI may misclassify reasons. Always verify numbers before sending financial summaries externally.
Use-case deep-dives
When Stripe MCP speeds up customer refund decisions
A 6-person support team handling 40-60 refund requests daily needs to check payment history, subscription status, and dispute records before approving. The Stripe MCP pulls transaction context into the AI workspace so agents see the full payment timeline without tab-switching between Zendesk and the Stripe dashboard. OAuth2 auth means each agent connects their own Stripe account once, and the MCP respects their role permissions. This works when your refund policy has clear rules the AI can surface (amount thresholds, dispute history, subscription tenure). If your refunds require judgment calls beyond data lookup—like assessing customer tone or brand risk—the MCP still saves time but won't make the call for you. Best fit: teams processing structured refund decisions where speed matters more than edge-case nuance.
Why Stripe MCP falls short for monthly board decks
A 3-person founding team building their monthly investor update needs MRR, churn, and cohort retention pulled from Stripe. The Stripe MCP can fetch raw transaction and subscription data, but it won't calculate cohort curves or format charts for slides—you're still exporting to a spreadsheet or BI tool for the final analysis. OAuth2 setup is straightforward, but if only one founder has Stripe admin access, the others can't query independently. This MCP works for quick sanity checks during the month (did that enterprise deal actually close?) but doesn't replace your reporting stack. If you're already using Stripe Sigma or a tool like ChartMogul, keep those. The MCP is a lookup layer, not an analytics engine.
When Stripe MCP unblocks new customer activation
A 5-person onboarding team sees 10-15 customers weekly stuck at payment—card declines, SCA failures, invoice confusion. The Stripe MCP lets the team query payment attempt logs and subscription states without pinging engineering or waiting for a Stripe dashboard login. OAuth2 means each onboarding specialist authenticates once and gets read access scoped to their role. The AI can surface the exact decline reason or flag a missing payment method, so the specialist knows whether to email the customer or escalate to billing ops. This works when your payment flow is standard Stripe Checkout or Billing; if you've built a custom integration with webhooks and retries, the MCP sees Stripe's side but not your app's logic. Best for teams where payment friction is frequent but diagnosable from Stripe data alone.
Frequently asked
What does the Stripe MCP let me do in Switchy?
It connects your Stripe account so AI agents can read payment data, customer records, and subscription details without leaving the conversation. You can ask questions about revenue, refund a charge, or pull invoice history — the agent handles the API calls. It's faster than switching tabs to the Stripe dashboard for routine queries.
Do I need admin access to connect Stripe via OAuth?
You need a Stripe account with sufficient permissions to authorize the OAuth flow. Typically that means Owner or Admin role, since the MCP requests read and write scopes across payments, customers, and subscriptions. If you're on a restricted role, the connection will fail or return limited data.
Can the Stripe MCP create new products or update pricing?
Yes, if the OAuth scopes include write access to products and prices. The agent can create SKUs, adjust recurring billing amounts, or archive old plans. However, it won't touch your tax settings or payout schedule — those require manual changes in the Stripe dashboard for compliance reasons.
Why use this instead of just logging into Stripe directly?
You use it when you want AI to answer questions or take actions without context-switching. Instead of filtering the Stripe dashboard for "failed charges last week", you ask the agent and get a summary in seconds. It's not a replacement for deep financial review, but it eliminates repetitive lookups.
Who on my team should connect the Stripe account?
Whoever owns billing or finance operations. They'll authorize the OAuth connection once, and the whole Switchy workspace inherits access. If multiple people need to trigger refunds or check subscriptions, connect it under a shared service account so the integration doesn't break when someone leaves.