Cursor Integration

Cursor’s chat panel is MCP-aware. With one config entry, every CMDOP tool — terminal, files, ask_agent, board — becomes available inside the editor, and Cursor can reach across your fleet from a code review without leaving the IDE.

Prerequisites

CMDOP installed; cmdop login complete; the daemon online (cmdop agent status).
Cursor installed and updated to a version that supports MCP.
A repo open if you want a project-level integration; otherwise the user-level path is fine.

Cursor MCP config locations

Cursor reads two files; project-level wins over user-level:

Scope	Path	Use when
Project	`<repo>/.cursor/mcp.json`	Teammates should share the integration.
User	`~/.cursor/mcp.json`	Personal setup, all repos.

Add the CMDOP server entry


{
  "mcpServers": {
    "cmdop": {
      "command": "cmdop",
      "args": ["mcp", "stdio"]
    }
  }
}

Reload from the command palette (Cmd/Ctrl+Shift+P → “MCP: Reload servers”) or restart Cursor.

If cmdop is not on Cursor’s PATH, use the absolute path — which cmdop from your shell prints it.

Per-project vs per-user

Pick by who should see CMDOP in this repo:

Per-project — commit .cursor/mcp.json to the repo. Anyone cloning gets the integration. They still need their own cmdop login and their own running daemon — sharing the config does not share credentials.
Per-user — keep CMDOP private to your machine. Useful when only you are operating the fleet.

What tools you get

Cursor sees the same MCP surface Claude Desktop sees. The high-leverage ones in an editor context:

Tool	Why it pays off in Cursor
`execute_command`	Run a one-off script on `mac-studio` or `vps-audi` straight from the chat.
`ask_agent`, `ask_agents`	Fan out a debug query across your fleet without opening a terminal.
`read_file`, `grep`, `glob`	Pull context from a remote machine into the chat.
`issue_create`, `issue_update`	Open a board issue from a code-review thread.

See tools reference for the full list.

Workflows worth trying

One-off prod check from a PR review. “Run systemctl status nginx on vps-audi and tell me if config matches the diff.” Cursor calls execute_command against the right machine.
Cross-fleet diagnostic. “Ask every prod machine: do you see this stack trace in the last hour?” — single prompt, ask_agents fan-out.
Issue creation from review comments. “Open a board issue summarizing this thread and assign it to mac-studio for repro.”

Permissions still apply

The CMDOP gate fires for Cursor exactly like it does for Claude Desktop. Tighten it before exposing a fleet:


cmdop permissions mode strict
cmdop permissions allow 'read_file(/var/log/**)'
cmdop permissions allow 'execute_command(systemctl status *)'
cmdop permissions audit --tail 20

A denial surfaces in Cursor as a tool error. Read Agent Permissions for the rule grammar.

Reload without a full restart

After editing mcp.json, the command palette has “MCP: Reload servers” — Cursor re-spawns cmdop mcp stdio without quitting the editor.