Stripe's MCP server gives an AI agent tools to work with the Stripe API and to search Stripe's documentation and support articles. Rather than one tool per endpoint, it has stripe_api_search and stripe_api_details to find a method and its parameters, stripe_api_read for GET requests and stripe_api_write for POST, PATCH, PUT and DELETE, over a listed set of methods such as customers, products, prices, subscriptions, invoices, payment links, refunds and webhook endpoints. It also has an account tool, an analytics tool in preview, a documentation search and an implementation planner. The hosted server is https://mcp.stripe.com. For Claude Code the docs give: claude mcp add --transport http stripe https://mcp.stripe.com/ and then authenticate with OAuth through /mcp. Stripe's recommended route is its CLI, npm install -g @stripe/cli@latest followed by stripe agent setup, which configures the server and Stripe's skills for the agents it detects. The docs also cover Cursor, Claude Desktop, Codex, ChatGPT and VS Code. We would add it while building checkout or billing: the agent can look up the right API method, create test products and prices in a sandbox, and read back what a payment actually did. The page labels it Public preview. Stripe asks you to enable human confirmation of tools and to take care when combining it with other servers, because of prompt injection. Some writes, such as refunds, need your approval through a link before they run. From October 31, 2026, key-based access only accepts Agent keys; plain secret keys and untagged restricted keys will be refused.
The log is the half nobody can write on their own: an entry lands here the moment somebody names this tool in one. Attach it from the composer’s + menu.
Nobody has said anything about Stripe MCP yet.
Nobody has rated Stripe MCP yet. What it is like to build with is the part no download count can tell anyone.