Connect the Stripe MCP server to Unblocked to give AI agents live payments and billing context

Billing bugs are hard to reason about from code alone: a failed renewal, a duplicate charge, or a webhook that never fired only makes sense next to the actual Stripe objects and events involved. Engineers end up copying IDs between the Stripe Dashboard and their editor. Stripe’s MCP server exposes Stripe API data and documentation to AI agents, and Unblocked connects to it once so every agent can look up a payment or subscription without its own Stripe setup.

This is a third-party MCP server: Stripe hosts and maintains it, and Unblocked connects to it as a verified MCP server. Nothing is ingested or indexed — Unblocked calls the read-only tools you select at the moment a question needs them, so answers reflect your Stripe account as it is now, not a copy of your customer or payment records.

Wiring Stripe’s MCP server straight into an agent gives it raw API reads. Unblocked’s Context Engine reasons across those results and your other sources — following a failed invoice payment to the webhook handler that processed its events, the pull request that last changed that handler, and the support ticket the customer opened — and returns one cited answer.

Once connected, any MCP-compatible coding agent — Claude Code, Cursor, Devin, GitHub Copilot, Codex — reaches Stripe context through a single Unblocked MCP server connection.

What you get

• Live Stripe objects and events — Agents read customers, charges, PaymentIntents, subscriptions, invoices, disputes, and events through Stripe’s own MCP server, using the API’s read methods.
• Stripe docs alongside your integration — Agents can search Stripe’s documentation and API method details, so answers about your billing code draw on both your implementation and Stripe’s reference.
• Read-only, tool-level control — Stripe’s write tools — API writes, refunds, money movement, and company formation — are never offered. You choose which read tools Unblocked may call. Change the selection anytime from Settings → Data Sources.
• Context Engine reasoning — Stripe results are reconciled with your code, pull requests, support tickets, and conversations, so an odd charge or failed renewal leads to the code path behind it — with citations.

Prerequisites

• An Unblocked account (free to start).
• A Stripe account with MCP access enabled for your team, and permission to authorize Stripe’s OAuth consent or create an agent API key for the live mode account or sandbox you want to query.
• An MCP-compatible coding agent (Claude Code, Cursor, Devin, etc.) to use the context in your editor.

Step 1: Connect Stripe to Unblocked

1. In Unblocked, go to Settings → Data Sources → Connect another data source, and under Customer & Product select Stripe.
2. The Stripe MCP server URL is filled in for you. Choose OAuth, click Connect, and sign in to Stripe to authorize Unblocked.
3. Once Unblocked discovers the server’s tools, select the read-only tools it may use and click Save Settings.

Step 2: Install the Unblocked MCP server

On macOS or Linux, one command auto-detects and configures the supported agents on your machine:

On Windows, or when you prefer remote MCP, add the server manually using the configuration below, or follow the manual install guide .

claude mcp add -s user --transport http unblocked https://getunblocked.com/api/mcpsse

{
  "mcpServers": {
    "unblocked": {
      "url": "https://getunblocked.com/api/mcpsse"
    }
  }
}

https://getunblocked.com/api/mcpsse

Stripe hosts and maintains this MCP server. Unblocked calls only the read-only tools you select, at the moment a question needs them:

• stripe_api_readReads data with any supported Stripe API GET method, such as listing or retrieving customers, charges, subscriptions, invoices, disputes, and events.
• stripe_api_searchSearches for Stripe API methods by keyword.
• stripe_api_detailsReturns detailed parameter information for a specific Stripe API method.
• get_stripe_account_infoRetrieves details of the connected Stripe account.
• search_stripe_documentationSearches the Stripe documentation for a given question and language.

To give Claude Code, Cursor, GitHub Copilot, Codex, or another MCP-compatible AI coding agent access to Stripe context, connect Stripe to Unblocked and add the single Unblocked MCP server to your agent.

Unblocked acts as the MCP context layer for your Stripe data, searching customers, payments, and subscriptions alongside your other connected sources and returning cited results through these tools:

• context_researchResearches a question across your connected sources and calls the Stripe tools you selected when payments, subscriptions, invoices, or events are relevant, returning a synthesized answer with citations.
• context_get_urlsFetches the full content behind URLs your agent encounters across connected sources — Jira, Linear, Notion, Confluence, Slack, GitHub, and more.

Questions you (or your agent) can ask Unblocked about your Stripe data:

• Why did this customer’s subscription renewal fail, and which webhook handler processed the invoice events?
• Which events did Stripe send for this PaymentIntent, and did a recent pull request change how we handle them?
• What disputes are open right now, and is there a Zendesk ticket or Slack thread about any of them?
• Which prices does the Pro product have in Stripe, and does our checkout code reference the current ones?