MCP runtime for Cursor and Claude
Rig's local MCP hub connects Cursor, Claude Code, Codex, Windsurf, or VS Code to the processes you are actually running on your computer — not a guess from chat history. Ninety-five scoped tools cover create_project and groups, Compose, WordPress wp_inspect (themes, plugins, post types, WooCommerce when active), open_adminer, share_live_link, list projects, stream logs, read health, diagnose crashes, free ports, restart services, git status, env profiles, database snapshots, and fleet controls across linked machines. The hub listens on localhost with a revocable token; you choose full, control, or read access per editor. Source never leaves the machine. Install is one click from the desktop app or an npx one-liner. Pair with Rig Cloud ACP when you also need fleet status inside Zed; MCP remains the local coding loop for day-to-day diagnosis and restarts on the machine in front of you.
- 95 scoped MCP tools — not a raw shell
- Localhost hub with revocable token and access modes
- Works with Cursor, Claude Code, Codex, Windsurf, VS Code
- Source stays on disk; mutating tools need confirm: true
Does MCP get a raw shell on my computer?
No. Tools are scoped to project runtime context — processes, ports, logs, git, env, WordPress WP-CLI, Adminer — with access modes you control. Mutating WP-CLI and Live Links need confirm: true.
Which editors work?
Any MCP client: Cursor, Claude Code, Codex CLI, Windsurf, VS Code, and others via pasteable JSON or one-click install.
Can agents create a WordPress site or open Adminer?
Yes. create_project with template wordpress, wp_inspect for inventory, open_adminer for loopback DB UI, and share_live_link for client preview — Adminer and DB ports cannot be Live Linked.