Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP-to-ACP bridge — let any MCP client drive ACP coding agents
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"mcacp": {
"command": "npx",
"args": [
"-y",
"mcacp"
]
}
}
}在终端中运行这条命令
claude mcp add mcacp -- npx -y mcacp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mcacp": {
"command": "npx",
"args": [
"-y",
"mcacp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mcacp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcacp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Oortonaut 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.3)于9个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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