Use Site Check with Claude
Site Check ships as a Claude Code plugin and as a Claude Desktop MCP server. Wire it up once and ask Claude things like "Check the site pantheon.io" or"Is example.com ready to migrate?".
Claude Code (CLI)
Recommended path. Two commands and you're done — no API keys, no config.
# Add the marketplace (one-time)
/plugin marketplace add https://github.com/pantheon-systems-ps/site-check-mcp.git
# Install the plugin
/plugin install site-check
Try it
- "Check the site pantheon.io"
- "Run a Lighthouse audit on example.com"
- "Is example.com ready to migrate to Pantheon?"
Claude Desktop
Manual MCP install — four steps. macOS paths shown; Windows uses %APPDATA%\Claude\claude_desktop_config.json.
1 Clone the repo
git clone https://github.com/pantheon-systems-ps/site-check-mcp.git \
~/Git/site-check-mcpSkip if you already have it cloned.
2 Build the MCP server
cd ~/Git/site-check-mcp/server
npm install && npm run buildOr just run start.sh — it auto-builds on first launch.
3 Edit the Desktop config
Open this file (create it if it doesn't exist):
"~/Library/Application Support/Claude/claude_desktop_config.json"The path has a space — quote it if pasting into a shell.
Add the site-check entry to your mcpServers block:
{
"mcpServers": {
"site-check": {
"command": "node",
"args": [
"/Users/YOU/Git/site-check-mcp/server/dist/index.js"
]
}
}
}4 Restart Claude Desktop
Quit and reopen Claude Desktop. Click the hammer icon — you should see 15 Site Check tools listed.
Type "Check the security headers on pantheon.io" — Claude will call check_site automatically. If you don't see the tools, double-check the absolute path in args matches your clone location.
15 tools available
Claude picks the right one based on your prompt — no need to call them by name.