Skip to content

Client ID Metadata Document support #1150

New issue
New issue
Closed
Closed
Client ID Metadata Document support#1150
Assignees
cliffhall
Labels
authIssues and PRs related to authorizationenhancementNew feature requestv2Issues and PRs for v2

Description

@segevfiner
segevfiner
opened on Mar 16, 2026

Instead of DCR, newer spec also allows the use of Client ID Metadata Documents: https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#client-id-metadata-documents

It will be nice to support authenticating with servers using that when possible or the server doesn't support DCR.

I think this might require a public client ID metadata document, and hopefully compliant servers allow any port when localhost is specified with "application_type": "native", or otherwise running on the default localhost port, or one served from the MCP inspector itself, and the MCP server being inspected running alongside the MCP inspector so it can access it via localhost.

Activity

  1. lkesteloot commented on May 7, 2026

    @lkesteloot
    lkesteloot
    on May 7, 2026

    (Adding "CIMD" as a keyword so that this issue is searchable with that.)

  2. cliffhall
    added
    v2Issues and PRs for v2
    on Aug 1, 2026

  3. cliffhall commented on Aug 1, 2026

    @cliffhall
    cliffhall
    on Aug 1, 2026
    Member

    Triage: Priority = Medium

    Scored 7/16 with the priority rubric added to AGENTS.md in #1891, as part of the backlog triage in #1872. Added to project board #28 with Status Incoming — meaning filed and scored but not yet approved for work. A maintainer decides whether it moves to Todo.

    Axis Score Reasoning
    Severity / impact 3/5 A missing auth capability rather than a defect: servers that don't do DCR have no supported path here, but existing flows work.
    Urgency / staleness 3/5 Open since March 2026 with no movement — stale.
    Signal bonuses +1 high engagement (16 reactions — the most of any issue in this batch) (+1)
    Total 7 Lands in the Medium band (6-8).

    Related issues. One connected issue:

    Worth a second look. 16 reactions is by a wide margin the strongest demand signal in the open backlog, and the rubric only lets that count for +1. If demand should outweigh the axes, this is the issue that argues for it.

    Scores are a starting point, not a verdict — the rubric is meant to be overruled when it's plainly wrong, provided the reason is written down.

  4. symdeb commented on Aug 3, 2026

    @symdeb
    symdeb
    on Aug 3, 2026

    IMHO Medium is too low for a feature in the new spec to test against for a tool specially designed for testing the features against a specification and promoted on several blogs and vlogs and youtube channels.

  5. cliffhall
    added this to the v2.3.0 milestone on Aug 5, 2026
  6. cliffhall
    added
    authIssues and PRs related to authorization
    enhancementNew feature request
    on Aug 5, 2026

  7. cliffhall commented on Aug 11, 2026

    @cliffhall
    cliffhall
    on Aug 11, 2026
    Member

    There is already support for CIMD built into the V2 Inspector.

    Client Settings Icon

    Image

    OAuth Client Metadata Document Settings

    Image
  8. cliffhall
    removed this from the v2.3.0 milestone on Aug 11, 2026
  9. cliffhall
    self-assigned this
    on Aug 11, 2026
  10. cliffhall
    closed this as completedon Aug 11, 2026
  11. cliffhall
    modified the milestone: v2.2.0 on Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

authIssues and PRs related to authorizationenhancementNew feature requestv2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions