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

Open source

Browse source
This commit is contained in:
tadasant 2025-06-25 14:33:19 -07:00 • committed by Toby Padilla
commit 9d041ad4d9
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/design_principles.md
View file

@ -4,7 +4,7 @@ These are the core constraints that guide the design of the MCP Registry. They a
## 1. Single Source of Truth
The registry serves as the authoritative metadata repository for publicly-available MCP servers, both locally-run (open source) and remote (open or closed source). Server creators publish once, and all consumers (MCP clients, aggregators, etc.) reference the same canonical data.
The registry serves as the authoritative metadata repository for publicly-available MCP servers, both locally-run and remote, open source and closed source. Server creators publish once, and all consumers (MCP clients, aggregators, etc.) reference the same canonical data.
## 2. Minimal Operational Burden
@ -36,4 +36,4 @@ The registry serves as the authoritative metadata repository for publicly-availa
- Start with MVP that provides immediate value
- Build foundation that supports future features
- Don't over-engineer for hypothetical needs
- Each milestone should be independently valuable
- Each milestone should be independently valuable