Add a standardized OAuth 2.1-based authentication specification for MCP sub-registries, aligned with the MCP Authorization Specification. This enables: - Private registry entries with access control - Permission-based server visibility - Client code reuse (clients can use their existing MCP auth implementation) The spec is intended for downstream sub-registries. The official registry remains public for reading. Fixes #751 --------- Co-authored-by: Claude <noreply@anthropic.com>
22 lines
No EOL
554 B
Markdown
22 lines
No EOL
554 B
Markdown
# Reference Documentation
|
|
|
|
Technical specifications and quick lookups for the MCP Registry.
|
|
|
|
## API Reference
|
|
|
|
- [Generic Registry API](./api/generic-registry-api.md)
|
|
- [Registry Authorization](./api/registry-authorization.md)
|
|
- [Official Registry API](./api/official-registry-api.md)
|
|
|
|
## server.json Reference
|
|
|
|
- [Generic server.json Format](./server-json/generic-server-json.md)
|
|
- [Official Registry Requirements](./server-json/official-registry-requirements.md)
|
|
|
|
## CLI Reference
|
|
|
|
- [Commands](./cli/commands.md)
|
|
|
|
## Quick Reference
|
|
|
|
- [FAQ](./faq.md) |