Setup

The simplest path is to let the desktop app do it: open SiteCMD, go to Integrations, and connect Codex. 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.

To wire it up by hand, Codex reads MCP servers from ~/.codex/config.toml in TOML (not JSON). Add this block (macOS path shown):

[mcp_servers.sitecmd]
command = "node"
args = [
  "--disable-warning=ExperimentalWarning",
  "/Applications/SiteCMD.app/Contents/Resources/sitecmd-mcp/sitecmd-mcp.mjs",
]

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, Codex can:

Read scan results for any project in SiteCMD
List open issues filtered by severity or category
Get fix prompts with full context for each issue
Check score trends to see if recent changes helped or hurt
List all projects and their current health scores
Get scan instructions for running a scan and comparing results when you need fresh data

Usage

After connecting, ask Codex to check your scan results:

codex "Check the latest SiteCMD scan for my-project and fix any critical issues"

Codex will read the scan data through MCP and apply fixes with context from SiteCMD’s Web Scan, Code Scan, update, and history data.