modelcontextprotocol / modelcontextprotocol/modelcontextprotocol
A list of Implementation Requirements for OAuth Client ID Metadata Document
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.3k
- Forks
- 1.8k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 25
Description
What's broken?
The spec is ambiguous or self-contradictory
Where in the spec or docs?
https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization/client-registration
What should happen?
MCP Clients should include property redirect_uris + at least one element in it (redirect_uri). redirect_uris is a JSON array that can be empty.
What actually happens?
A list of requirements include this
The metadata document MUST include at least the following properties: client_id, client_name, redirect_uris
Anything else?
No response
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
Open the linked Client Registration section and read the surrounding requirements for the client metadata document. Clarify whether redirect_uris must be present and non-empty, and ensure the wording is consistent with the statement that the array may be empty. Done means the requirement has one unambiguous interpretation.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100