Setting change
Stripe retires its local MCP and agent toolkit packages
Stripe stopped updating @stripe/mcp, @stripe/agent-toolkit and its AI SDK packages, security fixes included. Move to the hosted Stripe MCP server.
- Date
- Works with
- Any agent
What’s new
On 4 November 2026 Stripe marked five packages as deprecated: @stripe/agent-toolkit, stripe-agent-toolkit (Python), @stripe/mcp (the local MCP server you start with npx), @stripe/ai-sdk and @stripe/token-meter. The stripe/ai README says they "will receive no further updates, including security fixes". The last source stays readable under the git tag ai-packages-final.
Stripe points you to its hosted MCP server at https://mcp.stripe.com. You connect with an OAuth sign-in in your browser, or with an agent API key. Stripe's migration note says the hosted server "is not being shut down". For @stripe/ai-sdk and @stripe/token-meter, Stripe points to its Token Billing docs.
Why it matters
If your MCP settings start Stripe with npx @stripe/mcp, that setup will not get another fix, security fixes included. Stripe gives no date when the npm packages stop working. npm does not mark them as deprecated, so an install shows no warning. The official Stripe plugin for Claude Code already uses the hosted server, so it is not affected.
How to try it
First add the hosted server. In Claude Code, run claude mcp add --transport http stripe https://mcp.stripe.com/ and then type /mcp to sign in with OAuth. Or install the official plugin with claude plugin install stripe@claude-plugins-official. Then try a read-only request in a Stripe sandbox, as Stripe's migration note says. When the new connection works, remove the npx @stripe/mcp entry from your MCP settings.
Related
Source
Checked against the source on 5 Nov 2026