Skip to content

feat: add mcp oauth cimd support - #3406

Open
taciturnaxolotl wants to merge 1 commit into
mainfrom
mcp-oauth-cimd
Open

feat: add mcp oauth cimd support#3406
taciturnaxolotl wants to merge 1 commit into
mainfrom
mcp-oauth-cimd

Conversation

@taciturnaxolotl

@taciturnaxolotl taciturnaxolotl commented Jul 23, 2026

Copy link
Copy Markdown
Member

builds on #2911

this requires hosting this file at https://charm.land/.well-known/oauth-client.json or somewhere similar

{
  "client_id": "https://raw.githubusercontent.com/charmbracelet/crush/refs/heads/mcp-oauth/oauth-client-metadata.json",
  "client_name": "Crush",
  "client_uri": "https://github.com/charmbracelet/crush",
  "redirect_uris": [
    "http://localhost:40704/callback",
    "http://localhost:40705/callback",
    "http://localhost:40706/callback",
    "http://localhost:40707/callback",
    "http://localhost:40708/callback",
    "http://localhost:40709/callback",
    "http://localhost:40710/callback",
    "http://localhost:40711/callback",
    "http://localhost:40712/callback",
    "http://localhost:40713/callback"
  ]
}

Publishes a Client ID Metadata Document and offers it to authorization
servers first, falling back to dynamic client registration. CIMD is the
registration method preferred by the MCP 2025-11-25 spec and lets servers
show "Crush" with its metadata on the consent screen.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant