modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: clarify registry is for subregistries, not individual clients (#414)

Browse source 
Update FAQ to clarify that the registry is primarily designed for
subregistries rather than individual clients or end-users.

I saw MCP client applications were listed here, which I think is not
what we were intending.
This commit is contained in:
adam jones 2025-09-10 10:47:03 -07:00 • committed by GitHub
commit 64b7fc6408
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/reference/faq.md
View file

@ -27,11 +27,7 @@ No. The MCP Registry stores metadata about MCP servers and references to where t
### Who should use the MCP Registry directly?
The registry is designed for programmatic consumption by:
- MCP client applications (Claude Desktop, Cline, etc.)
- Server aggregators (Smithery, PulseMCP, Docker Hub, etc.)
- NOT individual end-users (they should use MCP clients or aggregator UIs)
The registry is primarily designed for programmatic consumption by subregistries (Smithery, PulseMCP, Docker Hub, Anthropic, GitHub, etc.). It is NOT currently intended for individual clients or end-users (they should use subregistries).
### Will there be feature X?