Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Stripe's MCP server covers both halves of working with payments: building against Stripe (documentation search over their vast API surface) and operating a Stripe account (customers, invoices, payment links, subscriptions, refunds and disputes as callable tools).
The docs half quietly matters most for developers. Stripe's API is enormous, versioned, and full of subtleties an LLM half-remembers — exactly the conditions for plausible-but-wrong integration code. The search_documentation tool grounds answers in current Stripe docs, turning "how do I handle SCA retries for subscription invoices?" from folklore into citation.
The operational half turns account chores conversational: "create a payment link for the annual plan", "how much did we refund last month?", "find the customer with this email and check their subscription state". For support and finance workflows, having these as approved-tool-calls rather than dashboard sessions compounds into real time savings.
Stripe being Stripe, the guardrails are thought through: the hosted server at mcp.stripe.com uses OAuth, the local variant runs with restricted API keys you scope yourself, and the tool list is curated rather than a blind mirror of every endpoint. Run it with a restricted key in test mode while you build; graduate the scopes deliberately. Money infrastructure deserves the same caution here as anywhere — and gets better affordances for it than most.
rk_) are per-resource. Grant read on customers and subscriptions while withholding write on charges, and build the key around the questions you actually intend to ask.--tools=all is convenient and blunt. Naming a subset instead shrinks both the risk surface and the number of tool definitions the model has to reason across before choosing one.rk_test_ key cannot reach a live customer, which makes it the correct place to rehearse anything that ends in an email to a human.Payment flows written against today's Stripe API, with sources.
Customer, subscription and refund state pulled mid-ticket.
Refund totals, invoice states and dispute queues without dashboard digging.
| Tool | What it does |
|---|---|
| search_documentation | Search current Stripe docs |
| list_customers / create_customer | Find and create customers |
| create_payment_link | Generate payment links for products/prices |
| create_invoice / finalize_invoice | Invoice workflows |
| list_subscriptions / update_subscription | Subscription state and changes |
| create_refund | Issue refunds |
| list_disputes | Review disputes |
| get_stripe_account_info | Account context |
claude mcp add --transport http stripe https://mcp.stripe.comA Stripe account. Remote: OAuth. Local: a restricted API key — test mode first, minimal scopes always.
| Variable | Description | Required |
|---|---|---|
| STRIPE_SECRET_KEY | Restricted API key for local mode (remote uses OAuth)e.g. rk_test_... | Optional |
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Turn software procurement research into a conversation — search, compare, and evaluate Marketplace listings.
Airwallex docs, API references and a live sandbox, wired straight into your coding agent.
A full federal and state 1040 calculation pipeline exposed as MCP tools.