The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Acp MCP Server listing page.
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:
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):
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:
The bridge speaks streamable-HTTP MCP and proxies to ACP's /govern/tool-use endpoint.
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.gsk_ API key (recommended for programmatic clients) — pass an ACP API key directly as 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.
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.