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.

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.

Related

https://userig.app/cursor-mcp

NewSnag is coming: client feedback for web agencies. Join the waitlist
ChangelogStatus
Download
Cursor & Claude MCP

Your AI tool stops guessing.

Cursor and Claude only see your code, so they guess what is running. Rig runs a local MCP hub that Cursor, Claude Code or Windsurf can ask what's actually running: real ports, real logs, real process health, instead of assuming from your code.

Download for Mac — it's freeInstall the Rig plugin

Free forever on your computer. Pay only for Mesh (Pro, $15 a month).

cursor · a real sessionlive
you › why is checkout 500ing for the client?
cursor › get_logs storefront — ECONNREFUSED :5432
cursor › get_health postgres — container stopped
cursor › start_project postgres ✓
cursor › The DB was down, restarted. Ask them to retry.
The problem

Your assistant reads the code, not the computer.

MCP (Model Context Protocol) is the standard way for an AI assistant to call tools. Without a tool that can see your running app, it works from whatever you paste into chat.

Without Rig
  • You paste a stack trace from ten minutes ago
  • It assumes Postgres is up because the code says so
  • It suggests killing a process by pid and hopes
  • Or it gets a raw shell and full run of your machine
With Rig's MCP hub
  • It reads live logs and health for the project you named
  • It sees which port each service holds right now
  • It can start or restart a service, and waits for your yes
  • Scoped tools only, never a raw shell

get_logsget_healthwho_owns_portstart_projectrestart_projectlist_projects

Set up once

One line in your MCP config.

Linking your editor should take a minute, not an afternoon. Click Link in the Rig desktop app, install the Rig plugin, or paste one entry into your MCP config.

Claude Code

Rig plugin for Claude

Adds Rig to Claude Code with ready-made commands for status, logs, health, start, stop and restart. Changes always ask first.

Claude plugin
Cursor

Rig plugin for Cursor

The same plugin packaged for Cursor, with rules that tell the agent to ask Rig instead of guessing. Or add the MCP server in one click.

Add to CursorCursor plugin
GitHub · open source

The public plugin

Rig-local/rig-plugin is open source, so you can read exactly what your agent gets.

View on GitHub
{ "mcpServers": { "rig": { "command": "npx", "args": ["-y", "@userig/mcp"] } } }

Works with Cursor, Claude Code, Windsurf, Codex, VS Code, and anything else that speaks MCP.

Every way to connect →MCP in Rig docs →

Stays local

Your logs and source never leave your computer.

The MCP hub runs on localhost. Whatever your AI tool asks for comes straight from Rig. Nothing routes through a third-party server.

Token

Revocable

Each editor links with a token. Rotate it and every editor is unlinked at once.

Access

Full, control or read

Pick how much each editor may do. A read-only editor can look but never change anything.

Confirm

Changes wait for a yes

Tools that start, stop or change things need confirmation before they run.

How the hub is secured →

What the hub actually exposes

Six of the tools, not a black box.

These six cover most debugging sessions. The full hub has 95 scoped tools, from WordPress and Adminer to Live Link, Compose, git, env profiles and your other machines.

The hub, live

Which editors are linked, what they may do, and every tool call as it happens.

01
rig / connections / mcp hublive
Cursor
full access
Claude Code
control
Windsurf
read only
Claude Code › get_health postgres
Claude Code › start_project postgres · waiting for your yes
Claude Code › start_project postgres · approved ✓

Listening on 127.0.0.1 · revocable token

ToolWhat it does
get_logsTail a project's stdout/stderr
get_healthProcess state, port, uptime
who_owns_portWhich project (if any) holds a port
start_projectBring a stopped project up
restart_projectBounce a running one
list_projectsEvery project Rig knows about

All 95 tools →What is MCP? →

Related

More on Rig and AI

AI & MCP

What your assistant can do with Rig, and the clients that work today.

AI & MCP

ACP for Zed

Fleet status for your linked machines inside Zed, through Rig Cloud.

ACP

MCP vs ACP

Which protocol does what, in plain English.

MCP vs ACP
Questions

Fair questions

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.

Other workflows

Rig for the way you work

Mac process manager

Every local process, its port and its log in one window, with crashes restarted for you.

See the workflow

Laravel + Valet

Keep Valet's .test domains. Rig watches the queue workers, Horizon and logs underneath.

See the workflow

Local WordPress

A fresh WordPress site in one click, with WP-CLI, the database and HTTPS built in.

See the workflow

For freelancers

Show a client the work running on your computer with a link, not a staging deploy.

See the workflow

For solo developers

Every side project on one board, back up after a reboot without touching a terminal.

See the workflow

Full stack local dev

Web, API, database and workers started in the right order with one button.

See the workflow

Give your AI tool the truth, not a guess.

One desktop app, one config line, and Cursor knows exactly what's running. macOS 13+ · no credit card.

Download for Mac — it's freeInstall the plugin