A list of Implementation Requirements for OAuth Client ID Metadata Document

Open Beginner friendly
#3,224 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
authentication, documentation

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.

Description

bug
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

Dominant language
TypeScript
Stars
9.3k
Forks
1.8k
Avg merge
1d 12h
Merged PRs (30d)
25

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/modelcontextprotocol

All issues in modelcontextprotocol/modelcontextprotocol

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.