omcp — an open protocol for connecting AI models to tools and data.
Every revolution begins with a single act of defiance.
— Heveena, The Orville, “Sanctuary” (2019)
Build without permission.
omcp is a community-driven hard fork of the Model Context Protocol specification. It exists to keep the protocol an open, permissionless standard: developed asynchronously, reviewed transparently on GitHub, and decided on technical merit rather than on closed-door approval.
Read the manifesto.
This repo contains the:
- omcp specification
- omcp protocol schema
- omcp documentation
The schema is defined in TypeScript first, but made available as JSON Schema as well, for wider compatibility.
The specification is published as HTML and PDF — every version, plus every proposal — at
enclawed.github.io/omcp. It is generated from this
repository on every change to main; nothing there is written by hand. To build it yourself, run
npm run build:spec. See Published Specification.
omcp is drop-in compatible with the broader Model Context Protocol ecosystem. The wire protocol, schema field names, method names, and protocol version identifiers are unchanged, so existing clients, servers, and SDKs interoperate without modification. The fork is in how the specification is developed and governed, not in what goes over the wire.
omcp only ever adds. New capability arrives as an extension, or as an optional element that an implementation which does not understand it ignores. That is a standing constraint on every contribution, not an aspiration: a change that alters or removes what MCP defines is out of scope, whatever its merits.
There is no sponsor to find, no working group to join, and no approval to request. A pull request is judged on five things: it follows good coding practices, it solves a real problem that is not already addressed, it clearly states that problem, it ships working unit tests — along with the data needed to run them — that anybody can verify independently, and it ships its chapter for the reference documentation.
See CONTRIBUTING.md.
omcp is actively developed, hosted, and maintained by Enclawed, Inc., to the benefit of everyone. It is an independent fork of the original work, built together with its contributors, and is not affiliated with or endorsed by the upstream project.
The Model Context Protocol, which omcp forked, was created by David Soria Parra (@dsp) and Justin Spahr-Summers (@jspahrsummers).
omcp and the omcp logo are trademarks of Enclawed, Inc.
omcp is not affiliated with, endorsed by, or sponsored by the Model Context Protocol project, Anthropic, or LF Projects, LLC. "Model Context Protocol" and "MCP" are used here only to describe the protocol this project forked from and remains compatible with.
The code is open; the marks are not. You may state compatibility freely ("compatible with omcp", "an omcp server") and reproduce the logo unmodified when referring to the project. Naming your own product, service, or fork with the marks — or implying endorsement — needs permission. See TRADEMARK.md.
Code and specification contributions are licensed under the Apache License, Version 2.0. Documentation contributions (excluding specifications) are licensed under CC-BY-4.0. Some legacy contributions remain under the MIT License. See LICENSE for the full terms and NOTICE for attribution of the upstream work this project forked from.