Strict superset of MCP (Model Context Protocol) that adds protocol-level security, access control, and observability while maintaining full backward compatibility. Any valid MCP message is a valid MGP message. Any MGP server can operate as a standard MCP server when connected to a client that does not support MGP extensions.
| File | Sections | Content |
|---|---|---|
| docs/MGP_SPEC.md | §1 | Overview, Architecture, Migration Policy |
| docs/MGP_SECURITY.md | §2-§7 | Capability Negotiation, Permissions, Tool Security, Access Control, Audit, Code Safety |
| docs/MGP_COMMUNICATION.md | §11-§14 | Lifecycle, Streaming, Bidirectional Communication, Errors |
| docs/MGP_DISCOVERY.md | §15-§16 | Discovery, Dynamic Tool Discovery |
| docs/MGP_GUIDE.md | §17-§20 | Implementation, History, Patterns |
| docs/MGP_ISOLATION_DESIGN.md | (§8-§10 reserved) | OS-Level Isolation |
| docs/MGP_CONNECTOR.md | — | Connector Manifest (cloto-connector.json) v1 — companion to schemas/connector/v1.json |
mgp-validate tests MGP compliance for servers and clients. Compliance badges:
[MGP Tier 1] [MGP Tier 2] [MGP Tier 3] [MGP Tier 4]
See MGP_GUIDE.md §17.5 Staged Adoption Path for tier definitions and §17.8 for the validation tool.
ClotoCore is the reference implementation of MGP. See MGP_GUIDE.md §17.3 for the mapping of MGP specification sections to ClotoCore source-code locations.
- Current draft: v0.8.0-draft (2026-07-30)
- See CHANGELOG.md for version history
- License: MIT — this specification (and future SDKs) is MIT-licensed independently from ClotoCore (see MGP_GUIDE.md §17.4 License and Distribution Strategy)
Machine-readable schemas live under schemas/. Each schema has a stable $id under https://cloto.dev/schemas/.
| Schema | $id |
Companion doc |
|---|---|---|
schemas/connector/v1.json |
https://cloto.dev/schemas/connector/v1.json |
docs/MGP_CONNECTOR.md |
Additional schemas (isolation profile, audit event format, etc.) will be added as the ClotoHub integration roadmap advances.