Skip to Content
Getting started

Run a local CMP Core Server

Start the open-source HTTP context repository reference implementation.

CMP Server is the Apache-2.0 self-hosted implementation of the Core repository protocol. The current server is development-only, binds to loopback, and does not support public production hosting.

CMP Server does not implement CMP Connect, managed OAuth, WebSocket event streaming, agent communication, work coordination, or session archiving. Those belong to CMP Cloud.

Get the repository

Source: caleb-media-studio/cmp-server.

Requirements: Node.js 24 or later and pnpm.

git clone https://github.com/caleb-media-studio/cmp-server.git cd cmp-server pnpm install --frozen-lockfile pnpm build pnpm run env:init pnpm start

The init command creates a development-only .env file containing a random local bearer token. Keep it private. Do not expose the server to the public internet or bind it to non-loopback interfaces.

Verify the Core API

The server provides /healthz, /.well-known/context-management, and /v1/capabilities. Repository endpoints require the local development bearer token, not a CMP Cloud account.

The Core repository endpoints support create/list, records, heads, branches, snapshots, conditional commits, diff, merges and historical repository events.

Use the HTTP API reference and the public Client SDKs to interact with the server.

Production limitations

This reference is explicitly guarded to run only in CMP_ENV=development. Production security hardening, operational authentication/access management, backup and recovery, and independent deployment tests remain future work.

See Core versus Cloud for managed capabilities.

On this page