Safety
Stripe MCP stops taking full secret keys in December
Stripe's MCP server stops accepting full secret keys and untagged restricted keys after November 30, 2026; reconnect with OAuth or make an agent API key.
- Date
- Works with
- Claude Code, Codex CLI
What’s new
Stripe's MCP page now says "Migrate by November 30, 2026". From December, Stripe's hosted MCP server refuses full secret keys and restricted keys without the Agent tag. A request with one of these keys gets a 401 error.
Why it matters
If you connected Stripe to your assistant with a secret key, the connection stops working in December. With an OAuth sign-in or an agent API key, you do not paste a full secret key into your assistant, and you can remove the access later.
Stripe also tells you to keep tool approval on in your assistant.
How to try it
Run claude mcp add --transport http stripe https://mcp.stripe.com/ and then type /mcp to sign in with OAuth. If you use a key, make a new agent API key in your Stripe Dashboard.
Related
Source
Checked against the source on 15 Oct 2026