Zed

Zed has native MCP support in its Agent Panel. Add SiteCMD to your settings and enable its tools in the profile you use.

SiteCMD's in-app Integrations connect button currently writes config for Cursor, Claude Code, Codex, and Windsurf. For Zed, add the server by hand as below.

Configuration

Run zed: open settings file from the command palette and add the server under context_servers, with command and args at the same level. You can also use Settings → AI → MCP Servers → Add Server → Add Local Server. See Zed's MCP guide.

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.

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

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). Zed picks up the change on save, no restart needed. (Older Zed builds used a nested "command": { "path", "args" } form; the flat shape above is current.)

What you get

Once connected, Zed's AI assistant 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.