Knowledge base / AI & MCP

04 · Editors & agents

AI & MCP

Local MCP hub; Agent Client Protocol for Rig Cloud; Cursor, Claude, Codex, Zed, and friends.

Connect AI editors (MCP)Hub setup, tools list, and staying glued to the right project port.Connect editors via ACPAgent Client Protocol for Rig Cloud — status, devices, Mesh, and tickets from Zed or JetBrains.What MCP is in RigModel Context Protocol: scoped tools on your real processes.Connect CursorOne-click MCP link for Cursor.Connect ClaudeWire Claude to Rig’s MCP hub.Connect CodexOpenAI Codex via Rig MCP.Connect VS CodeMCP for VS Code / Copilot-style workflows.Connect WindsurfLink Windsurf to the Rig hub.Connect GitHub Copilot CLIOne-click link to Rig MCP for Copilot CLI.Connect OpenCodeLink OpenCode to Rig's local MCP hub.Connect PiSet up Pi with Rig MCP (streamable HTTP).Connect OpenClawUse Rig as a generic remote MCP server in OpenClaw.Connect AntigravityUse Rig as a generic remote MCP server in Antigravity.Connect LM StudioAttach LM Studio to Rig's MCP hub for tool calls.Connect HermesUse Rig as a generic remote MCP server in Hermes.MCP tools overviewWhat agents can call today.Project-scoped MCPKeep the agent on the right repo and port.MCP open_url gotchasWhy Rig refuses the wrong localhost.MCP activity logSee what the agent called.Guidelines for agents using RigPrompt patterns that keep MCP reliable.What ACP is in RigAgent Client Protocol: editor ↔ agent — not the same as MCP.Connect Zed via ACPWalkthrough: register Rig Cloud as an ACP agent in Zed settings.ACP setup (stdio and cloud)Local stdio from the repo, or the cloud service at acp.userig.app.ACP auth and tokensService bearer vs personal developer token — what each one unlocks.ACP vs MCP in RigWhen to use the local MCP hub vs the cloud ACP agent.

Works with

Available for any MCP client — including