VS Code does not have a built-in MCP client, but two popular extensions add MCP support. Use either depending on your workflow.

The fastest path either way is to let the SiteCMD desktop app write the config for you: open SiteCMD, go to Integrations, and connect your extension. The app registers the MCP server and runs it bundled inside the app via your local Node, so there is nothing to install separately. The manual fallbacks below point each extension at the same bundled server script.

Cline

Cline is a VS Code extension with native MCP support. See the Cline integration guide for setup steps.

Continue

Continue is a VS Code extension that supports MCP servers as context providers. To configure it by hand, add the following to your Continue config (~/.continue/config.json), pointing at the bundled server script. On macOS:

{
  "mcpServers": [
    {
      "name": "sitecmd",
      "command": "node",
      "args": ["/Applications/SiteCMD.app/Contents/Resources/sitecmd-mcp/sitecmd-mcp.mjs"]
    }
  ]
}

Reload VS Code after saving.

What you get

Once connected via either extension, your AI assistant can call these tools:

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