modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
registry/docs/design/roadmap.md
Jonathan Hefner 43d41a242e
 Prepare docs for modelcontextprotocol.io (#728) 
This PR reorganizes and extends the existing documentation in
preparation for publishing on https://modelcontextprotocol.io/.

The current plan is for docs to remain in this repo, and be synced to
the `modelcontextprotocol/modelcontextprotocol` whenever necessary
(e.g., accompanying a release of the registry). I have included a script
in
https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1725
(`bin/pull-registry-docs.sh`) that can be run manually to perform the
sync.

If we later decide to permanently move the docs to the
`modelcontextprotocol/modelcontextprotocol` repo, that also works.

This PR puts all https://modelcontextprotocol.io/ docs into
`docs/modelcontextprotocol-io/`. Docs outside that subdirectory, such as
`docs/administration/admin-operations.md`, are intended to be accessible
solely via this repo. One major exception is the
`docs/reference/server-json/` subdirectory, which will depend on the
resolution of
https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1649.
However, I think we could address that in a follow-up PR.

---------

Co-authored-by: Adam Jones <adamj+git@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
2025-11-18 17:22:31 +00:00

1.7 KiB
Raw Permalink Blame History

MCP Registry Roadmap

This is a high-level roadmap for the MCP Registry. It is subject to change and not exhaustive, but it outlines the general thinking of the sequencing and scope of our work in this repository.

This roadmap may occasionally drift out of date. Please review Issues (and corresponding Labels) for the most current work in progress.

Current Status

The initial version of the MCP Registry is actively being developed. The initial focus is on delivering a REST API to which server creators can publish, and aggregator/marketplace consumers can ETL.

Phase 1: MVP/Go-Live (Current Focus)

See the go-live blocker issues.

Backlog (Future Work, may be moved to out of scope)

  • UI implementation
  • Store and surface other data besides servers (e.g. clients, resources)
  • Download count tracking
  • Internationalization (i18n)

Out of Scope (Not Planned)

  • Source code hosting: The registry will never host actual server code
  • Quality rankings: No built-in server quality assessments or rankings
  • Curation: No editorial decisions about which servers are "better"
  • Unified runtime: Not solving how servers are executed
  • Server hosting: The registry does not provide hosting for servers
  • Search engine: The registry will not provide a commercial grade search engine for servers
  • Server tags or categories: Not supported, to reduce moderation burden
  • Server rankings: The registry will not rank servers by subjective measures of quality