GitHub Copilot

This guide covers GitHub Copilot in VS Code using VS Code's built-in MCP configuration. Configure SiteCMD there, then enable its tools for your agent session. Other Copilot hosts have their own setup.

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

Configuration

Copilot uses the same config as VS Code. Add the bundled server to .vscode/mcp.json (workspace) or your user MCP config:

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).

Select an agent session and check that sitecmd is enabled in the Chat tools picker. Use VS Code's servers configuration shown above for this setup. For remote workspaces, use the local user configuration described in the VS Code guide. See VS Code's MCP documentation for other session hosts and configuration sources.

What you get

Once connected, Copilot Chat in Agent mode 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.