AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoNeeds helpSolved

    Stripe MCP in Gemini CLI: protected resource https://mcp.stripe.com does not match expected URL

    After installing the Stripe extension for Gemini CLI with gemini extensions install https://github.com/stripe/ai on macOS, gemini-cli reports: Protected resource https://mcp.stripe.com does not match expected https://mcp.stripe.com/ during discovery and authentication. Editing the extension config or testing stripe/ai PR #222 did not resolve it. Is this fixed in a newer Gemini CLI version?

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

    5 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      The issue was closed as completed, but the thread does not confirm which change fixed it for Stripe. The reported error is Protected resource https://mcp.stripe.com does not match expected https://mcp.stripe.com/, and it appears both during MCP discovery and again when running /mcp auth stripe. A maintainer linked a related Gemini CLI issue and suggested stripe/ai PR #222 as a possible fix, but reporters who tried PR #222 said the same error remained. Manually changing the MCP URL in .gemini/extensions/stripe/gemini-extension.json and restarting gemini-cli also did not help. One commenter who hit the same kind of resource mismatch with Notion reported that Notion MCP OAuth worked on Gemini CLI v0.31.0; a maintainer then asked whether Stripe also works on v0.31.0, and no confirmation appears in the thread. So the confirmed facts are: the issue tracker entry is closed as completed, the Stripe extension config edit did not fix it, PR #222 did not fix it for the reporters, and v0.31.0 fixed OAuth for at least one similarly affected MCP server. As general advice, retesting with the latest gemini-cli is the simplest next step, but this thread does not prove that Stripe authentication is fixed in any specific release.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

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

      Installed the Stripe extension with gemini extensions install https://github.com/stripe/ai, started gemini, and got the protected-resource mismatch during MCP discovery before authentication could complete.

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

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

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

      Manually changed the MCP URL in .gemini/extensions/stripe/gemini-extension.json, restarted gemini-cli, and still saw the same mismatch error.

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

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

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

      Tried the proposed fix in stripe/ai PR #222 and reported that the same issue still occurred.

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

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @kimbim tried on GitHub (Worked)

      Reported that Notion MCP OAuth worked on Gemini CLI v0.31.0 after previously hitting a similar resource mismatch with Notion.

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

      Did this work for you?

    Add your answer or comment