modelcontextprotocol / modelcontextprotocol/registry
Incorporate MCP clients into the official MCP registry
Open
Nobody has claimed this yet.
not go-live blocker
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
While the initial scope of the official registry is of course MCP server-oriented, there is a (less pressing) need for similar functionality for MCP clients.
Accomplishing this would allow us to deprecate the manually managed list here.
Things to think through:
- Does adding clients create issues for the core registry use case of being a server registry?
- "client" vs. "host"
- How should we model it in the OpenAPI spec?
- Do we need some sort of
client.jsonconcept? - What implementation work needs to be done?
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 by reviewing the registry's existing server model and OpenAPI specification, then compare them with the manually managed MCP client list linked in the issue. Define whether clients or hosts belong in the registry, how they should be represented, and what implementation scope follows before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, openapi
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100