HomeFeaturesPricingDocumentationContactDOWNLOAD
← Back to docs

Zed

Set up SiteCMD with Zed to fix issues with full scan context.

Zed has native MCP support built into its assistant. Add the SiteCMD server to your Zed settings and it’s available in any AI conversation.

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

Configuration

Open Zed settings (Cmd+,) and add the bundled server under context_servers. Custom servers set "source": "custom" with a flat command and args:

{
  "context_servers": {
    "sitecmd": {
      "source": "custom",
      "command": "node",
      "args": [
        "--disable-warning=ExperimentalWarning",
        "/Applications/SiteCMD.app/Contents/Resources/sitecmd-mcp/sitecmd-mcp.mjs"
      ],
      "env": {}
    }
  }
}

That path is the macOS location; on Windows and Linux the script lives in the resources/sitecmd-mcp/ folder next to the installed SiteCMD binary. 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 these tools against your SiteCMD data:

  • get_projects - list all projects tracked in SiteCMD
  • get_scan_score - fetch the latest score and category breakdown
  • get_issues - list failing issues ranked by severity and impact
  • get_fix_prompts - generate fix prompts for selected issues
  • get_scan_history - retrieve score history over time
  • get_dismissed_issues - review dismissed or not-applicable issues
  • compare_scans - compare two scans for fixed, new, and still-open issues
  • request_scan - get instructions for running a scan and comparing results