Stripe MCP in Cursor still has sk_live in the config: what to do

1. Open the Cursor MCP config and find the old Stripe entry

Open ~/.cursor/mcp.json for all projects, or .cursor/mcp.json in a project, and find the Stripe entry that runs npx @stripe/mcp with an --api-key argument. The local @stripe/mcp and @stripe/agent-toolkit packages are deprecated and will receive no further updates, including security fixes.

2. Remove the entry and the key value

Remove that whole entry: the command, the --api-key argument, and the key value. Keep a note of the key's last characters only, so you can identify it in the Dashboard. Never copy the full value anywhere new.

3. Decide whether the old key was exposed

If that mcp.json was committed to a repo, pasted into chat, screen-shared, or sent to anyone, treat the key as leaked. Rotate it now in the Dashboard with expiration Now, and check its request logs, following Leaked Stripe secret key: what to do. Removing the file does not un-leak a key.

4. Reconnect with the hosted server and OAuth

Replace the entry with the URL only, then sign in with OAuth when Cursor prompts you and grant only the account or sandbox and permissions you need. Stripe's Cursor example is that URL on its own, in ~/.cursor/mcp.json, with no key in the file.

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

5. If the client cannot use OAuth, pass an agent API key from the environment

If the client cannot use OAuth, create an agent API key in the Dashboard with only the permissions it needs. You can spot these keys by the Agent badge. Pass it as the bearer token in the Authorization header, referenced from an environment variable. Never paste the full key into mcp.json.

Cursor resolves ${env:NAME} in command, args, env, url, and headers. For this header, that is Bearer ${env:AGENT_API_KEY} when the variable is named AGENT_API_KEY. Set that variable in your shell or system environment. Cursor does not load an envFile for a remote HTTP server. Stripe's Claude Code example uses Bearer ${AGENT_API_KEY}, and Stripe's example for other clients uses {{AGENT_API_KEY}}. Those are not Cursor's interpolation. Do not paste them into Cursor's mcp.json.

{
  "mcpServers": {
    "stripe": {
      "url": "https://mcp.stripe.com",
      "headers": {
        "Authorization": "Bearer ${env:AGENT_API_KEY}"
      }
    }
  }
}

6. Test the new configuration in a sandbox

Confirm the Stripe tools connect and read test data before you touch the live key.

7. Expire the old key

Once the sandbox test passes, expire the sk_ or untagged rk_ key the local package was using. Do it immediately if you already rotated it because the file was exposed. Unsupported keys get a 401 response with an OAuth discovery challenge once the December change lands.

8. Check the same key did not leak a second way

Search the project copy of .cursor/mcp.json, any committed copies, and your live site. Run a free SniffPup scan of the site you own. If the same secret shipped in your JavaScript or a public .env file, rotate it as leaked.