ACP · Agent Client Protocol

Your editor, talking to Rig Cloud.

Agent Client Protocol is how Zed and JetBrains plug in an agent. Rig’s cloud ACP agent answers fleet questions (status, devices, Mesh, tickets) without pasting dashboards into chat. Local coding still goes through MCP.

zed / agent panel · Rig Cloudlive
What’s up on my fleet?
3 machines enrolled. mac-mini awake, 4 projects running. studio-mac asleep on Mesh. 1 open ticket.
Restart the api on mac-mini.
I can only read your fleet from here. Starting and stopping goes through Rig MCP in your coding agent.
What you can ask

Three things it is for

01

Status

Ask what’s up on Rig Cloud without opening another tab.

02

Fleet

List enrolled machines, Mesh, and open tickets with your Rig session.

03

Not MCP

Local start/stop/logs stay on the MCP hub in Cursor and friends.

AI & MCP
ACP vs MCP

Two protocols. One product.

MCP · local

Agent ↔ Rig tools on this machine

Scoped logs, ports, restart. Hub on localhost, so it can act on the projects running in front of you.

AI & MCP
ACP · editor

Editor ↔ agent

Rig’s cloud agent for fleet context in Zed / JetBrains. It answers from Rig Cloud, not from your laptop.

ACP vs MCP docs
MCPACP
Who talks to whomYour coding agent and Rig on this computerYour editor and Rig’s agent in Rig Cloud
Where it runsThe hub on 127.0.0.1Rig Cloud (stdio in Zed, or cloud HTTP/WebSocket)
What it can doRead, or start, stop, restart and more, with your yesRead status, devices, Mesh and tickets
EditorsCursor, Claude, Codex, Copilot CLI, Windsurf, VS Code and moreZed and JetBrains
Get started

Three steps in Zed.

  1. 01

    Add the agent

    Add agent_servers pointing at apps/acp with ACP_MODE=stdio.

  2. 02

    Add your token

    Set RIG_TOKEN from Account → Security (developer tokens) for devices and tickets. Treat it like a password and never paste it into an AI chat.

  3. 03

    Ask

    Open a Rig Cloud thread and ask for status or your fleet.

Honest limits

What it doesn’t do

Not a coding agent

It won’t edit your repo. Pair it with your usual coding agent for that.

Not Cursor’s path today

Cursor still links via MCP. ACP is for editors that speak the protocol natively.

Remote ACP is early

Cloud HTTP/WebSocket works; editor support for remote agents is still catching up, so prefer stdio in Zed.

Questions

Common questions

Is ACP the same as MCP?

No. MCP is how an agent calls tools on your computer through Rig’s local hub. ACP is how an editor talks to an agent. Rig’s ACP agent answers Rig Cloud questions — fleet, status, Mesh, tickets — not local start/stop.

Does Cursor use Rig ACP?

Cursor and most coding agents use Rig MCP today. ACP is for editors that speak Agent Client Protocol — Zed and JetBrains first.

Is this NodeBB’s admin panel?

No. In older Rig docs ACP sometimes meant the forum Admin Control Panel. Agent Client Protocol is a different thing entirely.

Fleet context in the editor you already use.

Add Rig’s ACP agent to Zed in three steps, then ask about your machines in plain words.