Connect Sitechecker to Claude Code

Use your terminal to connect Claude Code directly to Sitechecker MCP. No directory listing, Sitechecker API key, or local MCP server is required.

Before you start

• Have a paid Sitechecker Basic, Standard, Premium, or Custom plan. Trial accounts are not eligible.
• Install the CLI using the official Claude Code installation instructions, then sign in. Having Claude Desktop installed does not by itself confirm that the claude terminal command is available. Your organization must permit this MCP connection.

Open a new terminal and run claude --version. If the command is not found, follow the installer’s PATH instructions. Alternatively, use the full executable path shown by the installer. On macOS and Linux, the native installer normally uses ~/.local/bin/claude; substitute that path for claude in the commands below if needed.

Server URL:

https://mcp.sitechecker.pro/mcp

Add Sitechecker

Run:

claude mcp add --transport http --scope user sitechecker https://mcp.sitechecker.pro/mcp

The user scope makes the connection available across your local Claude Code projects. sitechecker is its name.

If claude mcp list shows Needs authentication, the server has been added but still needs authorization. Continue with the next step.

Authorize access

Start Claude Code with claude, then enter:

/mcp

Select sitechecker and authenticate. Sign in to Sitechecker in the browser, approve access, and return to Claude Code. Check that the connection is authenticated.

Test the connection

Ask:

List my accessible Sitechecker projects and their IDs.

Choose a returned project and ask:

Compare its latest Site Audit with the previous crawl. Show the score change and changed issues.

If the connection does not work

Check /mcp for authentication or connection errors. If your organization blocks the server, contact your Claude administrator.

Sitechecker support: support@sitechecker.pro.

Claude Code MCP documentation