Cline - SiteCMD Docs

Cline is a VS Code extension with native MCP support. Connect it to SiteCMD so Cline can pull scan results and generate fix prompts as part of its agentic workflow.

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

Configuration

The easiest path is Cline’s own UI: open the MCP Servers panel (the plug icon), choose Configure MCP Servers, and add the sitecmd entry. That opens Cline’s settings file, where you can also edit it directly:

macOS / Linux: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Windows: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

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 script 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). If you run VS Code Insiders, VSCodium, or Cursor, the settings folder is named for that build (Code - Insiders, VSCodium, Cursor) instead of Code.

What you get

Once connected, Cline 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.