CHAP Coordinator — Claude Code MCP server
This MCP server records human decisions around AI agent work, including approvals, edits, overrides, and escalations.
claude mcp add --env CHAP_DB_PATH=<CHAP_DB_PATH> --env CHAP_PROFILES=<CHAP_PROFILES> --transport stdio coordinator-mcp -- npx -y @brightbeamai/chap-coordinator-mcpWhat CHAP Coordinator does
CHAP Coordinator makes a CHAP workspace available to MCP clients. It publishes 39 operations as tools named chap.<method>, uses JSON Schema for their inputs, and routes calls to the Coordinator. Agents can therefore record human decisions and address multiple workspaces by ID.
The package runs through npx over stdio. Install it locally with npm install @brightbeamai/chap-coordinator-mcp; Node 20+ is required. Configure the server with CHAP_DB_PATH and CHAP_PROFILES.
Without CHAP_DB_PATH, the coordinator stays in memory, so workspaces and decisions disappear when the client restarts. A configured database path also requires better-sqlite3; if that native dependency cannot load, the server exits instead of silently switching to volatile storage. The adapter itself has no authentication; OAuth 2.1 is attached at the Streamable HTTP transport layer.
What it helps with
- record an agent action approval
- store human edits and overrides
- route disputed work to escalation
- keep decisions across client restarts
- address several workspaces by ID
Example prompts for the agent
- Record my approval of the agent’s current action in CHAP.
- Save this change as a human decision in the active workspace.
- Escalate the disputed action through CHAP and show the result.
How to install CHAP Coordinator
Platform CLI
claude mcp add --env CHAP_DB_PATH=<CHAP_DB_PATH> --env CHAP_PROFILES=<CHAP_PROFILES> --transport stdio coordinator-mcp -- npx -y @brightbeamai/chap-coordinator-mcpReplace <…> with your own values
Platform CLI
codex mcp add coordinator-mcp --env CHAP_DB_PATH=<CHAP_DB_PATH> --env CHAP_PROFILES=<CHAP_PROFILES> -- npx -y @brightbeamai/chap-coordinator-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"coordinator-mcp": {
"command": "npx",
"args": [
"-y",
"@brightbeamai/chap-coordinator-mcp"
],
"env": {
"CHAP_DB_PATH": "<CHAP_DB_PATH>",
"CHAP_PROFILES": "<CHAP_PROFILES>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"coordinator-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@brightbeamai/chap-coordinator-mcp"
],
"env": {
"CHAP_DB_PATH": "<CHAP_DB_PATH>",
"CHAP_PROFILES": "<CHAP_PROFILES>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e CHAP_DB_PATH=<CHAP_DB_PATH> -e CHAP_PROFILES=<CHAP_PROFILES> coordinator-mcp npx -y @brightbeamai/chap-coordinator-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about CHAP Coordinator
How do I install CHAP Coordinator in Claude Code?
Run claude mcp add chap -- npx -y @brightbeamai/chap-coordinator-mcp.
What does CHAP Coordinator do?
It connects CHAP to an MCP client and exposes its operations as chap.<method> tools. An agent can use them to record human approvals, edits, overrides, and escalations.
Will the server keep decisions after a restart?
Yes, when CHAP_DB_PATH points to SQLite and better-sqlite3 loads successfully. Without that path, the coordinator uses memory and loses workspaces after restart.
