Stripe MCP stops full-access secret keys in December. Rotate to agent keys by November 30
Stripe's MCP docs say to migrate by November 30, 2026: from December, the MCP server rejects full-access secret keys and restricted keys that lack the Agent tag. Money-moving tools still need human confirmation.

Stripe documents a November 30, 2026 migration deadline for Model Context Protocol clients: in December the Stripe MCP server stops accepting full-access secret keys and restricted keys without the Agent tag. Use agent API keys (Agent badge) or OAuth; unsupported keys return 401 with OAuth discovery. Money-moving actions such as refunds and Treasury send/transfer/convert still require human confirmation via an approve URL that expires in 24 hours. Inventory every Cursor, Claude and Codex connection to Stripe before the cutover—not after the first 401 in a demo.
The December cutover
Stripe's MCP documentation, read November 5, 2026, tells teams to migrate by November 30, 2026. In December, the Stripe Model Context Protocol server stops accepting full-access secret keys and restricted keys that do not carry the Agent tag. Supported paths are agent API keys—the ones that show an Agent badge in the Dashboard—or OAuth. Keys that are not supported return HTTP 401 along with OAuth discovery metadata so a well-behaved client can start the right login.
That is a deliberate narrowing. MCP plugged Stripe into AI clients such as Cursor, Claude and Codex. Pasting a sk_live god-mode secret into a desktop agent was always a bad idea; December makes it a hard failure. If the key still has god-mode rights, the agent did not get safer when you pasted it into MCP.
Money-moving tools stay behind human confirmation: refunds and Treasury send, transfer and convert require an approve URL. That approval expires in 24 hours. Read that as product policy, not as optional UX.
Decision guide
What stops working vs what replaces it
| Consideration | Before / rejected | Supported path |
|---|---|---|
| Full-access secret key | Rejected in December. | Agent API key or OAuth |
| Restricted key, no Agent tag | Also rejected. | Agent-badged key |
| Money-moving tool call | Needs human confirm. | Approve URL, 24h expiry |
| Wrong key at runtime | HTTP 401. | OAuth discovery metadata |
The key that still works next month
Inventory every place Stripe credentials meet an AI client.
Local developer machines. Cursor MCP configs, Claude desktop connectors, Codex skills, shell env files, 1Password items copied into .env. Replace full-access secrets with agent keys scoped to the tools you actually need.
Shared team configs. A single restricted key without the Agent tag that "everyone uses for demos" will 401 in December. Issue per-environment agent keys and rotate the shared one out.
CI and automation. Some pipelines borrowed MCP patterns or Stripe keys meant for agents. Separate "build bot" keys from "interactive agent" keys. Do not reuse a human's OAuth session in CI.
Vendor-hosted agents. If a third-party support or ops agent talks to Stripe through MCP or a Stripe plugin, ask which auth mode they use and whether they will meet the November 30 guidance. Their delay becomes your outage.
Old restricted keys. Restricted is not the same as Agent-tagged. Confirm the badge in the Dashboard. If it is missing, create a new agent key and retire the old one.
Log each entry: who owns it, which Stripe account, which tools, last rotated, replacement due date. November 30 is the migration target Stripe publishes; do not discover the December rejection in a customer demo.
If the key still has god-mode rights, the agent did not get safer when you pasted it into MCP.
Human confirmation is not optional chrome
Stripe's MCP money-moving path asks a human to open an approve URL for refunds and Treasury send/transfer/convert. The URL expires in 24 hours. Design your runbooks around that.
Support refunds. An agent may prepare the refund; a named human still clicks approve. Put the ticket ID in the approval note so audit makes sense later.
Treasury moves. Same pattern, higher blast radius. Dual-control belongs in your policy even when the tool only requires one click.
Expired approvals. If someone ignores the URL for a day, the action does not silently succeed later. Train the team that "the agent said it refunded" is not evidence—the Dashboard and the approval event are.
Pair this with the same spend discipline we use for agent budget and price-drop checkout and agent checkout authority: tools that can move money need a person in the loop on purpose.
A two-week migration plan
Day 1–2: Export Stripe API keys; flag full-access and non-Agent restricted keys; list every MCP client config in eng and ops.
Day 3–5: Create agent keys per environment; wire OAuth where interactive users are the right model; update docs and 1Password.
Day 6–8: Point Cursor/Claude/Codex configs at the new keys; run a refund dry-run that stops at the approve URL.
Day 9–10: Revoke old secrets; confirm 401 on a deliberate wrong-key test; notify support and finance.
Day 11–14: Watch for shadow configs on laptops; add the November 30 date to the shared eng calendar.
If a contractor laptop still has sk_live in an MCP JSON file after you rotate Dashboard keys, you are not done. Search the repo and the MDM inventory.
Sequence of work
Two-week key migration
- Days 1–2
Inventory keys and MCP configs.
- Days 3–5
Issue agent keys; set OAuth.
- Days 6–8
Retarget clients; dry-run refund.
- Days 9–14
Revoke old secrets; hunt shadows.
Where teams slip
They rename a secret and call it done. The Agent tag and OAuth paths are the documented replacements. A renamed god-mode key still fails the policy intent.
They skip Treasury. Refunds get attention; Treasury tools get forgotten until someone tries a transfer in chat.
They leave demo keys in slide decks. Screenshots of Dashboard key pages in Notion are an incident waiting for a forward.
They treat 401 as a client bug. When December arrives, the first 401 is the cutover working. Have the runbook ready instead of filing a Stripe ticket in panic.
If Stripe sits inside your agents
Finish the inventory this week. Land agent keys or OAuth before November 30. Keep human confirmation in the refund and Treasury paths on purpose. If you need help wiring Stripe MCP into a broader business automation agent stack with real key hygiene, get in touch.
One more practical note before you close the tab. Put the deadline on a shared calendar with a named owner, not a channel that everyone watches and no one owns. Committees do not ship carton changes, agent pilots or CDN cutovers. A single person who can say "green" or "blocked on X" keeps the work from restarting every Monday with the same open questions.
When you brief leadership, lead with the operating decision, not the vendor announcement. Executives do not need another slide about artificial intelligence or carrier math. They need to know what changes at the bench, in checkout, in the partner portal or in the release train—and who is accountable for the before-and-after measurement.
Keep a short evidence packet next to every change: the primary source URL, the date you verified it, the SKUs or environments in scope and the rollback path. That packet is what you bring to the QBR, the board update or the incident review. Memory and Slack threads are not evidence.
If outside help would finish the inventory, the redesign or the cutover faster than waiting for a quiet week that never comes, bring them into the first scoping conversation with the right TWIMCO team rather than after the first red invoice or console banner. Scheduled migrations beat emergency freezes.
Write the "what good looks like" line in the same doc as the deadline. Green means a measured outcome—cartons repriced, keys rotated, banners cleared, agents stuck behind a real gate—not a meeting that ended on time. Share that definition with whoever will inherit the work when you are out.
Related work: Paddle8.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.