CHAP Coordinator MCP Server

What the code does

We read the source, 16 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    proc = subprocess.run([node, os.path.join(_VENDOR, "render.js")], input=json.dumps(specs),

            path = os.path.join(directory, f"{name}.csv")

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add chap -- npx -y @brightbeamai/chap-coordinator-mcp

{
  "mcpServers": {
    "chap": {
      "args": [
        "-y",
        "@brightbeamai/chap-coordinator-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.chap]
command = "npx"
args = ["-y", "@brightbeamai/chap-coordinator-mcp"]

{
  "mcpServers": {
    "chap": {
      "args": [
        "-y",
        "@brightbeamai/chap-coordinator-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "chap": {
      "args": [
        "-y",
        "@brightbeamai/chap-coordinator-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CHAP_DB_PATH (Path to a SQLite file. Without it the coordinator runs in memory and workspaces are lost when the client restarts.), CHAP_PROFILES (Comma-separated CHAP profiles enabled on new workspaces. Defaults to Core plus review, whisper, deliberation, handoff, control, routing, modes and audit-scitt.). The author declared them in the registry entry; get the values from the project itself.