HomeFeaturesPricingDocumentationContactDOWNLOAD

GitHub Copilot

Set up SiteCMD with GitHub Copilot to fix issues with full scan context.

GitHub Copilot’s agent mode reads MCP servers from VS Code’s own mcp.json, so there’s no separate Copilot setting to configure. Set up the VS Code server once and Copilot picks it up.

SiteCMD’s in-app Integrations connect button currently writes config for Cursor, Claude Code, and Codex. 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).

Two things to know: MCP tools only work in Copilot’s Agent mode, not Ask or Edit. And tools are off until you enable sitecmd in the tools picker in the Chat view. There is no github.copilot.chat.mcpServers setting; the mcp.json servers key is the only place Copilot looks.

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.