The OAuth callback URL is never shown on the MCP connection form

Source: Quick-sync-up-AgentZ call, 20 Jul 2026 (Atharva Shah, Murtaza Udaipurwala, Rahul Jadhav)
Suggested labels from the call: mcp ux good-first-issue p0

When you're setting up a client ID and secret for an MCP server, the provider (GitHub, in this case) asks you for a callback URL to register. That URL is something AgentZ controls and already knows. But the form doesn't show it anywhere, so Atharva had to guess what it might be. He guessed wrong, which is directly what caused the "MCP reports connected when it isn't" bug.

The fix. Print the actual callback URL right there on the form, in a copyable field. Murtaza called this one out as easy: "that's an easy one."

Why it's worth prioritizing. It's a small fix for a problem that's currently unguessable, and it's the direct root cause of a more serious bug elsewhere in the MCP setup flow.

Start by locating the MCP connection form and its OAuth setup flow. Confirm how the actual callback URL is obtained, then display that URL in a copyable field on the form. Done means a provider can register the shown URL without guessing and the form's behavior remains intact.