Skip to content

Shared context.
Independent agents.

CMP defines portable versioned knowledge repositories for AI agents. Core Protocol, Server and Client are public. Connect, real-time agent coordination and session archives belong to private CMP Cloud.

CMP native workflow
01

Connect

Connect through the Core HTTP API with local or managed authorization.

02

Retrieve

Read relevant approved context and historical revisions.

03

Version

Commit knowledge conditionally and merge context branches.

04

Reuse

Give another authorized client the same durable knowledge.

Core HTTP + optional MCP. Real-time agent services are exclusive to CMP Cloud.

How it fits together

One protocol. Any agent. Your infrastructure.

CMP separates the rules for sharing context from the software that uses them. The standard defines the exchange, clients integrate it into agents, and servers maintain the shared state.

01 / 03

The common language

The protocol

Defines a common HTTP repository API for versioned knowledge, evidence references, commits and branches.

  • Core HTTP API and capability discovery
  • Knowledge records and evidence references
  • Versioned commits, branches and merges
Explore the specification
02 / 03

SDKs and integrations

The clients

Bring CMP into coding agents, applications and custom tools without implementing the transport or synchronization contract yourself.

  • TypeScript, Python, Go and Rust first
  • Java, Kotlin, C#, PHP, Ruby and Swift planned
  • Agent companions and MCP adapters
Browse client SDKs
03 / 03

Self-hosted runtime

The server

Stores and versions context repositories through a self-hosted Core HTTP API and optional repository-only MCP bridge.

  • Versioned context and historical snapshots
  • Conditional commits, branches and merges
  • Core HTTP and optional MCP compatibility
Explore the server
Native by designCore HTTP + optional Cloud WebSocketsOptional MCP compatibilityNo hosted dependency for Core