Connect SiteCMD to Claude Code so it can read scan results and generate targeted fix prompts directly from the CLI.

Configuration

Recommended - let the desktop app do it:

Open SiteCMD, go to Integrations, and connect Claude Code. The app writes the config and runs the MCP server bundled inside the app via your local Node, so there’s nothing to install and the script path is resolved for your OS.

Manual fallback:

To wire it up by hand, register the bundled server with the claude mcp add command (macOS path shown):

claude mcp add --scope user sitecmd -- node /Applications/SiteCMD.app/Contents/Resources/sitecmd-mcp/sitecmd-mcp.mjs

That edits Claude Code’s config at ~/.claude.json. On Windows and Linux the script lives in the resources/sitecmd-mcp/ folder next to the installed SiteCMD binary; letting the app write the config is the reliable way to get the path right.

What you get

Once connected, Claude Code 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