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:

{
  "servers": {
    "sitecmd": {
      "type": "stdio",
      "command": "node",
      "args": [
        "--disable-warning=ExperimentalWarning",
        "/Applications/SiteCMD.app/Contents/Resources/sitecmd-mcp/sitecmd-mcp.mjs"
      ]
    }
  }
}

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.

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