HomeFeaturesPricingDocumentationContactDOWNLOAD

VS Code

Set up SiteCMD with VS Code to fix issues with full scan context.

VS Code has built-in MCP support, so Copilot’s agent mode can read your SiteCMD scan results once you point it at the bundled server.

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

Configuration

Create .vscode/mcp.json in your workspace (or open your user config with MCP: Open User Configuration from the Command Palette) and add the bundled server. The top-level key is servers, and stdio servers set "type": "stdio":

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.

{
  "servers": {
    "sitecmd": {
      "type": "stdio",
      "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). MCP tools are available in Copilot’s Agent mode (see GitHub Copilot). The Cline extension uses its own setup, covered in Cline.

Note: VS Code uses the servers key, not the mcpServers key that Cursor and Claude Desktop use. Pasting an mcpServers block here won’t work.

What you get

Once connected, your AI assistant (VS Code) 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.