Your editor, talking to Rig Cloud
Rig Cloud speaks Agent Client Protocol (ACP) so editors like Zed and JetBrains can ask about your fleet without pasting dashboards into chat. ACP is the editor-to-agent protocol; MCP is how agents call tools on your Mac. Rig’s ACP agent answers status, devices, Mesh, and support tickets. It is not a coding agent and not NodeBB’s admin panel. Prefer local stdio in Zed today; the cloud endpoint at acp.userig.app exposes HTTP and WebSocket with a service bearer. Pair ACP with MCP: coding stays on the local hub, fleet context comes through ACP.
- ACP = editor ↔ agent; MCP = agent ↔ local Rig tools
- Zed / JetBrains first; Cursor still uses MCP
- Cloud endpoint at acp.userig.app — stdio recommended for Zed
- Not a coding agent — fleet and status context only