Typeform MCP connection fails before the approval screen - callback address mismatch #58403

Activity

1. opencode-agent commented on Oct 23, 2026

   

   opencode-agentBot

   on Oct 23, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report, and for passing on Typeform support's diagnosis. It made the cause clear right away.

   I think this is a duplicate of #50510. It's the same problem: OpenCode identifies itself with https://opencode.ai/oauth/opencode/client.json, which lists only http://127.0.0.1/callback and http://localhost/callback. The redirect URI it actually sends is http://127.0.0.1:<port>/mcp/oauth/callback, so authorization servers that check the path exactly reject the request. This affects v2 as well as 1.19.3.

   Possible duplicates and related issues, ordered by likelihood:

   • mcp: cimd client.json redirect_uris don't match the loopback callback, breaking Exa OAuth #50510: same mismatch between client.json and the callback, reported for Exa (open)
   • mcp: CIMD client.json redirect_uris don't match the loopback callback, breaking Turso MCP OAuth #54421: same mismatch for Turso, already closed as a duplicate of mcp: cimd client.json redirect_uris don't match the loopback callback, breaking Exa OAuth #50510
   • Remote MCP OAuth fails against Figma: hardcoded callback path /mcp/oauth/callback rejected by Figma's DCR endpoint #57360: Figma rejecting the hardcoded /mcp/oauth/callback path

   A possible workaround, from #50510: set the redirect URI explicitly for the server in your config. OpenCode then registers its actual callback with Typeform instead of using client.json. That was confirmed on v2. On 1.19.3 the keys are camelCase, but I haven't confirmed the workaround applies there:

   "typeform": {
     "type": "remote",
     "url": "https://api.typeform.com/mcp",
     "oauth": {
       "callbackPort": 19876,
       "redirectUri": "http://127.0.0.1:19876/mcp/oauth/callback"
     }
   }

   It only helps if Typeform accepts dynamic client registration. A note on #50510 saying Typeform is affected too would show the problem isn't limited to one server.

   The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
2. opencode-agent

   added

   pending close

   triaging

   on Oct 23, 2026
3. neriousy

   closed this as completedin #58453on Oct 23, 2026
4. opencode-agent

   closed this as duplicateon Oct 24, 2026
5. opencode-agent commented on Oct 24, 2026

   

   opencode-agentBot

   on Oct 24, 2026 – with OpenCode Agent

   Contributor

   More actions

   We haven't heard back, so I'm closing this as a duplicate of #50510. The Typeform failure comes from the same mismatch: the hosted client.json lists http://127.0.0.1/callback and http://localhost/callback, but OpenCode sends http://127.0.0.1:<port>/mcp/oauth/callback. Please follow #50510 for updates. A short note there saying Typeform is affected would help show how widespread this is.

   Until then, the oauth.redirectUri / callbackPort config from the earlier comment might work around it, if Typeform accepts dynamic client registration. If your problem turns out to be different, reply here and we can reopen.