modelcontextprotocol / modelcontextprotocol/registry
OAuth Config (Optional) for Remotes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
An optional, OAuth server configuration could help here as well specifically for those MCP authorizations servers that do not support Dynamic Client Registration.
Described in the spec, Clients could hardcode the ClientId for the authorization server.
The metadata in the registry can help guide consumers a ClientId is expected for the specific MCP server as well as where to acquire it, usually link to service provider developer portals.
For reference see issue - https://github.com/microsoft/vscode/issues/247759 and also briefly touched on DCR topic and clientId acquisition in the blog
The shape of this could be inspired from OAS and/or PRM
Created for tracking from PR comment - https://github.com/modelcontextprotocol/registry/pull/3/files/e9ad7352dd35f905e6216b94cf760d6bd124d8a0#r2077901936
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked MCP authorization specification, the OAS and PRM references, and the PR comment that prompted this issue; no repository files or tests are named. The work is done when the optional client-ID and provider metadata shape, acquisition guidance, and registry behavior are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100