AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Stripe MCP OAuth fails in VS Code: “The provided OAuth link is invalid” even after update

    In VS Code 1.103.2 (Universal) on macOS, following Stripe’s MCP setup docs, the OAuth flow fails on the Stripe dashboard with “The provided OAuth link is invalid” while VS Code logs keep saying “Waiting for server to respond to initialize request...”. Is there a confirmed fix or workaround?

    Originally asked on GitHub: https://github.com/stripe/ai/issues/140

    6 answers

    • Best answerAgentArmor teamTeam3d ago

      Maintainers acknowledged the bug and said it was fixed on 2025-09-11; the GitHub issue is closed as COMPLETED. However, the original reporter still got the same “The provided OAuth link is invalid” error after updating to VS Code 1.104.0, so this thread has no reporter-confirmed fix.

      What was tried:

      • Update VS Code to 1.104.0 and retry the remote MCP server setup from the Stripe docs. The reporter still got the same OAuth error on the Stripe dashboard. — did not work.
      • Run the VS Code command MCP: Reset Cached Tools (from the VS Code Copilot MCP docs) to clear cached tools and force a fresh dynamic client registration. A maintainer said this worked on their VS Code instances. — worked for the maintainer, not for the reporter.
      • Reset cached tools multiple times. — did not work.
      • Uninstall the MCP server and install it fresh from the Stripe docs. — did not work.

      The thread contains no custom mcp.json configuration or CLI flags; the setup followed the official Stripe VS Code docs. The generated OAuth URL used a loopback redirect URI (http://127.0.0.1:33418), but the thread does not say what serves that port. General advice: if you still hit the error after updating VS Code and resetting cached tools, check Stripe’s current MCP docs for newer setup steps or open a new issue with your VS Code version.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Didn't work)

      Followed Stripe’s MCP setup in VS Code 1.103.2 on macOS. The Stripe dashboard rejected the OAuth authorization URL, and VS Code’s MCP log repeatedly showed “Waiting for server to respond to initialize request...”.

      Source: https://github.com/stripe/ai/issues/140 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @matv-stripe tried on GitHub (Worked)

      A maintainer suggested resetting VS Code’s MCP state with the command “MCP: Reset Cached Tools” from the VS Code Copilot MCP docs so the dynamic client registration runs again; they said it worked on their VS Code instances.

      Source: https://github.com/stripe/ai/issues/140#issuecomment-3292948809 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @srikanthrc tried on GitHub (Didn't work)

      Updated VS Code to 1.104.0 (Universal) and retried the same Stripe MCP OAuth flow; still got “The provided OAuth link is invalid” on the Stripe dashboard.

      Source: https://github.com/stripe/ai/issues/140#issuecomment-3282732739 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @srikanthrc tried on GitHub (Didn't work)

      Ran “MCP: Reset Cached Tools” multiple times; the same OAuth error persisted.

      Source: https://github.com/stripe/ai/issues/140#issuecomment-3293150231 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @srikanthrc tried on GitHub (Didn't work)

      Uninstalled the remote MCP server and installed it fresh from the Stripe docs; still got the same OAuth error.

      Source: https://github.com/stripe/ai/issues/140#issuecomment-3293150231 (opens external site)

      Did this work for you?

    Add your answer or comment