Stripe MCP server for Claude, Codex and Cursor

What your AI apps can do with Stripe

• Inspect permitted payment data
• Search Stripe documentation

Stripe MCP tools

15 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Suggested starting access

Toolstile read each Stripe tool's description and wrote these starting selections by hand. They are a suggestion reviewed by Toolstile, not a guarantee: Stripe decides what each tool does and can change it, so check that a selection fits each app before you save it.

Search Stripe documentation and API

Search the Stripe docs and API reference and plan an integration. No access to account data.

• Allow: search_stripe_documentation, stripe_api_search, stripe_api_details, stripe_implementation_planner

Read account data with approval

The same docs tools, with the account's details and each read of customers, payments or reports waiting for approval. Nothing that writes or moves money.

• Allow: search_stripe_documentation, stripe_api_search, stripe_api_details, stripe_implementation_planner
• Require approval: stripe_api_read, stripe_analytics, get_stripe_account_info

In the access editor, choosing a suggestion adds the listed tools this server offers to your draft. Existing access stays as it is, blocks and approval requirements stay in force, and the suggestion doesn't grant tool names the server adds later. Nothing is saved until you choose Save changes.

Suggested access for each AI app

The documentation this list comes from doesn't mark Stripe's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Stripe connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

1. Connect once. Add Stripe to a workspace (browser sign-in or access token). Toolstile keeps the credential, so no agent config holds it.
2. Choose access per app. Give Claude Code every Stripe tool, give Cursor only the read tools, or keep Stripe away from an app entirely.
3. Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
4. Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Stripe MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Stripe in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Stripe endpoint to each app separately. In Claude Code:

claude mcp add --transport http stripe 'https://mcp.stripe.com/'

In Cursor's mcp.json:

{
  "mcpServers": {
    "stripe": {
      "url": "https://mcp.stripe.com/"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Stripe MCP documentation for what your client needs.

Before you connect

A Stripe account. Use a restricted agent API key when choosing token authentication.

Server details

Stripe MCP documentation