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>
This commit is contained in:
parent
3d3337942b
commit
43d41a242e
1 changed files with 1606 additions and 1397 deletions
|
|
@ -10,7 +10,6 @@ While the [generic server.json format](./generic-server-json.md) defines the bas
|
|||
|
||||
- **Namespace authentication** - Servers are published under appropriate namespaces
|
||||
- **Package ownership verification** - Publishers actually control referenced packages
|
||||
- **Remote server URL match** - Remote server base urls match namespaces
|
||||
- **Restricted registry base urls** - Packages are from trusted public registries
|
||||
- **`_meta` namespace restrictions** - Restricted to `publisher` key only
|
||||
|
||||
|
|
@ -26,10 +25,6 @@ All packages must include metadata proving the publisher owns them. This prevent
|
|||
|
||||
For detailed verification requirements for each registry type, see the [publishing guide](../../guides/publishing/publish-server.md).
|
||||
|
||||
## Remote Server URL Match
|
||||
|
||||
Remote servers must use URLs that match the publisher's domain from their namespace. For example, `com.example/server` can only use remote URLs on `example.com` or its subdomains.
|
||||
|
||||
## Restricted Registry Base URLs
|
||||
|
||||
Only trusted public registries are supported. Private registries and alternative mirrors are not allowed.
|
||||
|
|
|
|||
Loading…
Reference in a new issue