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

Clarify the docs around _meta publisher extensions (#695)

Browse source
This commit is contained in:
Radoslav Dimitrov 2025-10-24 18:29:15 +03:00 • committed by GitHub
commit 0ef5b90ed7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 100 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/reference/server-json/generic-server-json.md
View file

@ -14,6 +14,22 @@ The schema contains all field definitions, validation rules, examples, and detai
The official registry has some more restrictions on top of this. See the [official registry requirements](./official-registry-requirements.md) for details.
## Extension Metadata with `_meta`
The optional `_meta` field allows publishers to include custom metadata alongside their server definitions using reverse DNS namespacing.
```jsonc
{
"_meta": {
"io.modelcontextprotocol.registry/publisher-provided": {
// Your custom metadata here
}
}
}
```
When publishing to the official registry, custom metadata must be placed under the key `io.modelcontextprotocol.registry/publisher-provided`. See the [official registry requirements](./official-registry-requirements.md) for detailed restrictions and examples.
## Examples
<!-- As a heads up, these are used as part of tests/integration/main.go -->