Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
See, price, and control every tool call your AI agents make: policy checks, cost, and audit tools.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.agenticcontrolplane.com/mcp在终端中运行这条命令
claude mcp add --transport http acp https://api.agenticcontrolplane.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"acp": {
"url": "https://api.agenticcontrolplane.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"acp": {
"type": "http",
"url": "https://api.agenticcontrolplane.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.agenticcontrolplane.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
发布者(agenticcontrolplane.com)不是仓库所有者(davidcrowe);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.3.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Georgia MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
An MCP server for Georgian public data, read from the organizations that publish it.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Model Context Protocol server that lets Claude, ChatGPT, Cursor, Lovable, and any MCP client check tool calls against Agentic Control Plane governance — policy decisions, rate limits, audit logs, identity attribution.
One sentence: before your AI agent runs a sensitive tool, it asks ACP whether the call is allowed. ACP says yes, no, or asks for confirmation, and writes an audit row attributable to the human behind the agent.
Two tools, callable via MCP:
| Tool | What it does |
|---|---|
acp_check | Answer "would this call be allowed?" for a specific call — for explicit questions or pre-flight planning. If ACP hooks are installed in the harness, tool calls are already governed automatically and this doesn't need to be called per tool. Returns allow / deny / ask plus a reason. |
acp_status | Verify the connection and your workspace identity. |
That's the whole surface. Everything else — policies, audit logs, scope intersection, delegation chains — runs server-side at api.agenticcontrolplane.com. This MCP server is just the bridge.
The server is hosted at `https://mcp.agenticcontrolplane.com/mcp`. Add it as a connector in your MCP client:
Claude Desktop / Claude.ai connector:
URL: https://mcp.agenticcontrolplane.com/mcp
Auth: OAuth (sign in with Google through ACP)
ChatGPT, Cursor, Lovable, Cline: Same URL, same OAuth flow. Most clients have a one-click "Add MCP Server" UI.
Programmatic clients (your own agent code):
POST https://mcp.agenticcontrolplane.com/mcp
Authorization: Bearer gsk_ Content-Type: application/json
You'll need an ACP workspace. The free tier is unlimited tool-call logging — sign up at cloud.agenticcontrolplane.com/login.
If you want to run the bridge yourself — for air-gapped deployments, or to point at a self-hosted ACP gateway — clone and run:
git clone https://github.com/agentic-control-plane/acp-mcp-server
cd acp-mcp-server npm install npm run build
export ACP_API_BASE=https://your-acp-gateway.example.com
export ACP_SERVICE_KEY=gsk_workspace_...
npm start
The bridge speaks streamable-HTTP MCP and proxies to ACP's /govern/tool-use endpoint.
your AI client this MCP server ACP gateway
───────────── ───────────────── ─────────── Claude / ChatGPT ──► mcp.agenticcontrolplane ──► api.agenticcontrolplane Cursor / Lovable POST /mcp (acp_check) POST /govern/tool-use ↓ policy + audit + identity ↓ allow / deny / ask
Every call writes an audit row attributable to the human identity behind the OAuth session — so you get a complete log of every governed tool call across every MCP client your team uses, in one workspace.
The server supports two authentication paths:
ACP_SERVICE_KEY to authorize the underlying governance call on the human's behalf.Authorization: Bearer gsk_.... The key's identity is the ACP-side actor. Skip OAuth.OAuth discovery metadata is served at /.well-known/oauth-protected-resource per the MCP authorization spec.
npm install
npm run dev # tsx-based hot reload
Tools are defined in src/tools/tools.ts. The MCP JSON-RPC handler is in src/handlers/mcpHandler.ts. The Express entry point and rate limits are in src/server/expressServer.ts.
MIT — see LICENSE.