# Stripe

> Canonical: https://www.yalc.ai/mcps/stripe/

Read revenue, customers, and subscriptions from Claude Code via the official Stripe MCP.

## Categories

- intelligence
- operations

**Website:** https://stripe.com/

**Repo:** https://github.com/stripe/agent-toolkit

## Glance

- Maintainer: Stripe (official)
- License: MIT
- Auth: API key (test or live)

**Install Command:** claude mcp add stripe --env STRIPE_SECRET_KEY=sk_xxx -- npx -y @stripe/mcp --tools=all

**Install Notes:** Generate a restricted API key in your Stripe dashboard (Developers → API keys → Create restricted key). Grant only the resources Yalc workflows need (typically customers:read, subscriptions:read, charges:read). Use a test key (sk_test_) for piloting before switching to live.

**Yalc Fit Score:** 8

**Yalc Verdict:** The revenue and customer truth layer. Pull MRR, churn, and customer states into Claude Code summaries without ever opening the Stripe dashboard.

## Plain Description

Stripe ships an official MCP server as part of their Agent Toolkit. The MCP exposes core Stripe resources (customers, subscriptions, charges, products, invoices, refunds) as native Claude tool calls. API key auth means setup is trivial. Restricted keys let you scope exactly what Yalc workflows can access.

The Claude Code Stripe MCP connects your Stripe account to Claude Code so you read revenue, customers, and subscriptions straight from a prompt. Add it with the official Stripe server and a restricted API key, then query billing data without opening the dashboard.

For Yalc operators running B2B SaaS, Stripe is the revenue source of truth. The MCP turns "what's my MRR this month", "show me at risk subscriptions", or "summarize last 7 days of new customers" into one-prompt operations. Pair with HubSpot or Notion for richer customer context.

## Yalc Framework

**Workflow Step:** listen

### Workflow Narrative

The Stripe MCP sits at the **listen** node when Yalc workflows need to know what's happening with revenue. Most reads are read only intelligence: MRR, new customers, churn risk, recent failed payments.

Pair with HubSpot (CRM) or Notion (state) for context-rich summaries. Pair with Slack to push weekly revenue digests. The MCP is read-heavy by design; production agents rarely write to Stripe except for refunds or customer metadata updates.

**Workflow Position:** The revenue and customer state layer. Yalc reads MRR, subscriptions, churn signals, and customer history. Writes are deliberate (refund a charge, update customer metadata) and gated.

### Prompt Patterns

- Yalc, give me MRR for this month broken down by plan. Compare to last month. Surface the 3 biggest expansions and the 3 biggest contractions.
→ Yalc reads subscription data via Stripe MCP, computes via Claude, returns digest.

- Yalc, list every customer with a failed payment in the last 7 days. Pull their HubSpot context, surface those at risk of churn, and draft outreach for each.
→ Yalc joins Stripe MCP failed payments with HubSpot contacts, drafts via Claude.

- Yalc, summarize new customers this week. Group by acquisition channel (use the customer metadata "source" field). Post to #revenue Slack channel.
→ Yalc reads Stripe customer creation events, classifies by metadata, posts via Slack MCP.


### Chaining

**Upstream:** Stripe webhook (subscription event) → Yalc workflow trigger

**Downstream:** Stripe MCP (read) → Claude (analysis) → HubSpot or Notion or Slack


### Anti Patterns

- Don't use a live key for piloting. Test keys (sk_test_) are isolated and prevent accidental writes to production billing data.
- Don't issue refunds via the MCP without human approval. Yalc workflows can draft and queue, but final refund click belongs to a human.
- Don't grant unrestricted API keys. Use restricted keys with minimal scopes. Stripe's IAM is granular; use it.


**Compatibility:** Official Stripe MCP runs in Claude Code, Claude Desktop, Cursor, and any MCP-compatible client. Stripe also publishes a Python and Node toolkit for direct integration outside MCP. The MCP wraps the same toolkit.

## Pros

- Official Stripe-maintained server. MIT licensed.
- API key auth (no OAuth dance).
- Restricted keys for scoped access. Production-safe by default.
- Test keys let you pilot in isolation before going live.
- Pairs cleanly with HubSpot or Notion MCPs for full revenue context.

## Cons

- Read-heavy by design. Mutations (refunds, plan changes) are exposed but should always be human-gated.
- Pricing is per Stripe API call standards (free for typical Yalc volume).
- Some advanced reporting (custom metrics, complex segments) is not in the MCP. Use Stripe Sigma for that.
- Webhooks for real-time events require a separate webhook handler outside the MCP.

## Who For

- Founders running B2B SaaS who want revenue snapshots without leaving Claude
- Operators tracking expansion and churn from natural language prompts
- Finance functions automating weekly digests across Stripe + CRM

## Related

### Mcp

**Rule:** Pair Stripe (revenue) with HubSpot (pipeline) for full customer context.

**Url:** /mcps/hubspot/



## Alternatives

- **Direct Stripe REST API**
  - Rule: Skip the MCP for headless cron jobs. Direct API is more efficient outside Claude conversations.
  - Url: #
- **Stripe Sigma**
  - Rule: Switch when you need SQL-style ad hoc reporting, not natural language summaries.
  - Url: #

## Faq

- Q: Should I use a test key or live key with the MCP?
  - A: Always start with a test key (sk_test_). Once you trust the workflow, switch to a restricted live key with minimal scopes.
- Q: How do I generate a restricted Stripe API key?
  - A: In your Stripe dashboard, go to Developers, API keys, Create restricted key. Choose only the resources Yalc workflows need (typically customers, subscriptions, charges as read).
- Q: Can the MCP issue refunds?
  - A: Yes, but Yalc workflows should always require human approval for refunds. The MCP exposes the verb; the discipline is in your prompts.
- Q: Does the MCP support Stripe Connect?
  - A: Yes. Multi-account scenarios (platforms billing on behalf of connected accounts) are supported via the standard Stripe-Account header. Set it via the MCP's environment.
- Q: How does the MCP handle webhooks?
  - A: It doesn't. The MCP is for reads and writes. For real-time events (subscription canceled, payment failed), set up a Stripe webhook endpoint that triggers your Yalc workflow.
- Q: Can I use the MCP across multiple Stripe accounts?
  - A: Yes. Register the MCP server multiple times with different STRIPE_SECRET_KEY values and different server names. Each Yalc workflow can route to the right account by name.

**Reviewer:** Othmane Khadri