Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP-to-ACP bridge — let any MCP client drive ACP coding agents
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.
You 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": {
"mcacp": {
"command": "npx",
"args": [
"-y",
"mcacp"
]
}
}
}Run this in your terminal
claude mcp add mcacp -- npx -y mcacpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mcacp": {
"command": "npx",
"args": [
"-y",
"mcacp"
]
}
}
}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": {
"mcacp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcacp"
]
}
}
}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.
These 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 Oortonaut, 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.1.3) reached the registry 9 months 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, Dialyne
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.
Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.
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.
Bridge any MCP client to any ACP coding agent.
MCACP is an MCP server that speaks the Agent Client Protocol on behalf of your MCP host. It lets Claude Code, Zed, VS Code, or any MCP-compatible client spawn, manage, and interact with ACP coding agents — turning a single chat window into a multi-agent control plane.
MCP Client (Claude Code, Zed, VS Code, ...)
| | MCP (stdio) v MCACP | | ACP (stdio, per agent) v Claude Code · Gemini CLI · Codex · Auggie · Copilot · ...
Run any ACP agent from any MCP client. You don't need a dedicated IDE plugin for each agent. Install Gemini from Claude Code. Run Codex from Zed. Mix and match.
Compare agents side by side. Give the same task to Claude Code ACP and Gemini CLI in parallel sessions and compare the results.
Build agent-driven pipelines. One agent writes code, another reviews it, a third runs the tests. MCACP handles the lifecycle and permission flow for all of them.
Control permissions interactively. On hosts that support MCP elicitation (Zed), permission requests pop up as interactive forms. On hosts that don't (Claude Code), they fall back to operator mode where the host agent decides.
Resume where you left off. Sessions persist to disk. Shut down, restart, load_session — the agent picks up where it stopped.
Discover and install agents from chat. Browse the ACP registry, install agents, check for upgrades — without leaving your conversation.
npm install -g mcacp
Or run directly:
npx mcacp
Claude Code (~/.claude/settings.json):
{
"mcpServers": { "mcacp": { "command": "npx", "args": ["-y", "mcacp"] } } }
Zed (settings.json):
{
"context_servers": { "mcacp": { "command": { "path": "npx", "args": ["-y", "mcacp"] } } } }
Then from chat:
"Search for available agents" → registry_search
"Install the Gemini agent" → agent_install "Initialize it and start a session" → initialize + new_session "Ask it to refactor auth" → prompt_start + prompt
MCACP exposes 22 tools organized into five groups.
| Tool | Description |
|---|---|
list_installed_agents | List locally installed agents |
registry_search | Search the ACP agent registry |
agent_install | Install an agent from the registry |
agent_uninstall | Remove an installed agent |
agent_check_upgrades | Check for available upgrades |
discover_agents | Scan editor configs (Zed, JetBrains) for agents |
reload_config | Reload mcacp.json from disk |
| Tool | Description |
|---|---|
initialize | Spawn an agent process and perform the ACP handshake |
shutdown | Gracefully shut down an agent |
| Tool | Description |
|---|---|
new_session | Create a session with working directory and permission policy |
load_session | Resume a persisted session |
list_sessions | List stored sessions for an agent |
close_session | Close a session (preserved for later resume) |
| Tool | Description |
|---|---|
prompt_start | Send a prompt (returns immediately) |
prompt | Block until events are available |
prompt_events | Non-blocking poll for events |
grant_permission | Resolve a pending permission request (operator mode) |
request_permission | Send an MCP elicitation to the host for a permission decision |
cancel | Cancel an in-progress prompt |
set_mode | Switch agent operating mode |
| Tool | Description |
|---|---|
list_running_agents | List all agents with status and sessions |
get_agent_status | Detailed status of a running agent |
set_agent_status | Set status text for an agent |
Each session can use a different policy:
| Policy | Behavior |
|---|---|
allow_all | Auto-approve all agent actions |
deny_all | Block all tool use |
elicit | Forward as MCP elicitations to the host; falls back to operator if unsupported |
operator | Queue as events — the host agent decides via grant_permission |
Orchestrator MCACP ACP Agent
| -- session/prompt ---------> | |
| <- request_permission ------ | |
| <- {pendingPermission: ...} | |
| -- grant_permission -------> | |
| {toolCallId, optionId} | -- permission outcome -----> |
| <- prompt result ----------- | |
| <- {stopReason, updates} |
MCACP looks for mcacp.json in these locations (first found wins):
--config flag or MCACP_CONFIG env var.mcacp/mcacp.json in the current directory~/.config/mcacp/mcacp.json{
"registries": ["https://cdn.agentclientprotocol.com/registry/v1/latest/registry.json"], "defaultPermissionPolicy": "elicit", "agent_servers": { "my-custom-agent": { "command": "node", "args": ["my-agent.js"] } } }
See docs/configuration.md for the full schema.
git clone https://github.com/Oortonaut/mcacp.git
cd mcacp npm install npm run build node dist/index.js
Apache-2.0