Codex

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

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.

[mcp_servers.sitecmd]
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, expanded to absolute paths. Letting the app write the config is the reliable way to get the path right.

What you get

Once connected, Codex 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.

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.