Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Auditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CHAP_DB_PATH, CHAP_PROFILESYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"chap": {
"command": "npx",
"args": [
"-y",
"@brightbeamai/chap-coordinator-mcp"
],
"env": {
"CHAP_DB_PATH": "your-value",
"CHAP_PROFILES": "your-value"
}
}
}
}Run this in your terminal
claude mcp add chap --env CHAP_DB_PATH=your-value --env CHAP_PROFILES=your-value -- npx -y @brightbeamai/chap-coordinator-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"chap": {
"command": "npx",
"args": [
"-y",
"@brightbeamai/chap-coordinator-mcp"
],
"env": {
"CHAP_DB_PATH": "your-value",
"CHAP_PROFILES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"chap": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@brightbeamai/chap-coordinator-mcp"
],
"env": {
"CHAP_DB_PATH": "your-value",
"CHAP_PROFILES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CHAP_DB_PATH envCHAP_PROFILES envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account BrightbeamAI, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.4) reached the registry 8 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Starreel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server adapter for the CHAP Coordinator. Wraps a Coordinator instance and exposes every CHAP method as an MCP tool, so any MCP client (Claude Desktop, Cursor, Claude Code, the rest) can drive a CHAP workspace directly.
Spec target: MCP 2026-07-28, serving MCP 2025-11-25 clients as well · CHAP 0.3.
The package ships a stdio server, so an MCP client can use CHAP without any code. Point the client at it:
{
"mcpServers": { "chap": { "command": "npx", "args": ["-y", "@brightbeamai/chap-coordinator-mcp"], "env": { "CHAP_DB_PATH": "~/chap.db" } } } }
All 39 methods arrive as tools named chap. . Two environment variables configure it:
| Variable | Effect |
|---|---|
CHAP_DB_PATH | Path to a SQLite file. Without it the coordinator runs in memory and every workspace is lost when the client restarts. |
CHAP_PROFILES | Comma-separated profiles for new workspaces. Defaults to Core plus review, whisper, deliberation, handoff, control, routing, modes and audit-scitt, so the audit chain is on from the first entry. |
Persistence needs better-sqlite3, an optional native dependency of the coordinator. If CHAP_DB_PATH is set and it cannot be loaded the server says so and exits rather than starting in memory and discarding the decisions it was asked to keep.
The server is also listed in the MCP registry as io.github.BrightbeamAI/chap.
npm install @brightbeamai/chap-coordinator-mcp
Node 20+ required. Runtime dependencies: @brightbeamai/chap-coordinator, @modelcontextprotocol/sdk and zod. The binary is chap-mcp-server.
import { Coordinator } from "@brightbeamai/chap-coordinator";
import { makeChapMcpServer } from "@brightbeamai/chap-coordinator-mcp"; import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
const coord = new Coordinator({ defaultProfiles: ["core/1.0", "review/1.0", "audit-scitt/1.0"], });
const server = makeChapMcpServer(coord, { name: "chap", version: "0.3.4" }); await server.connect(new StdioServerTransport());
The returned Server is the official MCP SDK's Server class with tools/list and tools/call handlers pre-registered. Attach any MCP transport (stdio, Streamable HTTP, etc.).
A runnable reference server is at reference/mcp-server-ts/.
All 39 CHAP methods become MCP tools named chap. . Each tool's inputSchema is the JSON Schema for the corresponding method's params. Tool descriptions are tuned for LLM consumption.
The chap. prefix avoids collisions with other MCP servers a client might have loaded simultaneously.
coord.dispatch().npm test
The integration tests use the SDK's InMemoryTransport.createLinkedPair() to drive a wrapped Coordinator end-to-end, exercising every major profile.
integrations/CHAP-with-MCP.mdexamples/drive-chap-from-claude-desktop.mdchap_coordinator.transports.mcp_serverApache 2.0. See the parent repository's LICENSE.