Cursor - SiteCMD Docs

Connect SiteCMD to Cursor so your AI assistant can read scan results, list issues, and generate fix prompts without leaving the editor.

Configuration

The easiest way is to let the desktop app do it: open SiteCMD, go to Integrations, and connect Cursor. The app writes the config and runs the MCP server bundled inside the app via your local Node, so there’s nothing to install and the script path is resolved for your OS.

To wire it up by hand, add the bundled server script to ~/.cursor/mcp.json (create the file if it doesn’t exist):

Requires Node 22.22.1 or newer on your PATH and the persistent server script; see what you need first for the path on each OS and why the flag is there.

{
  "mcpServers": {
    "sitecmd": {
      "command": "node",
      "args": [
        "--disable-warning=ExperimentalWarning",
        "/Users/<you>/Library/Application Support/com.sitecmd.app/sitecmd-mcp/sitecmd-mcp.mjs"
      ]
    }
  }
}

That path is the macOS location with <you> standing in for your username. On Linux use ~/.local/share/com.sitecmd.app/sitecmd-mcp/sitecmd-mcp.mjs and on Windows %LOCALAPPDATA%\com.sitecmd.app\sitecmd-mcp\sitecmd-mcp.mjs, both expanded to absolute paths (JSON needs \\ for Windows separators). Letting the app write the config is the reliable way to get it right. Restart Cursor after saving.

What you get

Once connected, Cursor’s AI can call every SiteCMD MCP tool: read the ranked issue list and fix prompts, pick up fix briefs, request verification, and compare scans before and after a change. The full list, with what each tool does, is in What SiteCMD exposes; Fixing with AI editors walks through the loop.