Skip to content

Show the OAuth redirect URI (with copy) in Server Settings for pre-registered clients #2524

Closed

Description

@cliffhall

Problem

A user who pre-registers an OAuth client (client ID + secret) with their authorization server has to register the Inspector's redirect URI there before connecting. The Server Settings → OAuth Settings panel never shows that value. Other MCP clients (Claude, ChatGPT) show it so it can be copied into the AS configuration. Right now users have to guess it or read the source.

With DCR the Inspector sends redirect_uris itself, so this only matters for pre-registered (static) clients.

Current behavior

  • Web: the redirect URI is ${window.location.origin}/oauth/callback (core/auth/browser/providers.ts:54), which is http://localhost:6274/oauth/callback by default. It follows the address bar, so 127.0.0.1 vs localhost, a non-default CLIENT_PORT or a non-local host all change it. Many authorization servers match redirect URIs exactly.
  • TUI/CLI: http://127.0.0.1:6276/oauth/callback by default (core/auth/node/runner-oauth-callback.ts), overridable via --callback-url / MCP_OAUTH_CALLBACK_URL.

Proposed

Add a read-only Redirect URI field with a copy button to the OAuth Settings section of the web Server Settings form. Compute it the same way the provider does, so the field cannot drift from the value actually sent. Add a short description noting that it depends on the origin the Inspector is opened from.

Out of scope: TUI/CLI surfaces. Their default is already fixed and documented in their READMEs.

Reported by a user asking whether the redirect URI is fixed and whether they should register it on their AS.

Activity

  1. added this to the v2.10.0 milestone on Sep 29, 2026
  2. cliffhall commented on Sep 29, 2026

    @cliffhall
    MemberAuthor

    Priority: Medium (6) — Severity 2 (minor friction; the workaround is knowing the URI is <origin>/oauth/callback) + Urgency 3 (wanted this milestone; user-reported) + 1 (milestoned) = 6.

  3. self-assigned this
    on Oct 5, 2026
  4. cliffhall commented on Oct 5, 2026

    @cliffhall
    MemberAuthor

    Shipped in #2586 (merged into v2/main). Verified alongside the other #2569 sub-issues in rollup #2596.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature requestv2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions