Codex

Connect directly to Sitechecker MCP from your terminal. You do not need a directory listing, an API key, or a local MCP server.

Before you start

• Have a paid Sitechecker Basic, Standard, Premium, or Custom plan. Trial accounts are not eligible.
• Install Codex CLI and sign in to Codex. Run codex --version to check that the command is available.

Server URL:

https://mcp.sitechecker.pro/mcp

Add Sitechecker

Open Terminal on macOS or a terminal on Windows or Linux and run:

codex mcp add sitechecker --url https://mcp.sitechecker.pro/mcp

Keep the terminal open while completing authorization. sitechecker is the connection name used in the commands below.

Authorize access

If Codex starts OAuth automatically, open the authorization link it displays. Sign in to the Sitechecker account containing your projects, approve the requested access, and wait for the success message in the terminal.

If authorization did not start, run:

codex mcp login sitechecker

Complete the same browser sign-in flow. You do not need to copy a token or API key.

Start using Sitechecker

Start a new Codex chat in the desktop app, or run codex to open a CLI session. If an already-open desktop app does not show the new connection, quit and reopen it.

Ask:

List my accessible Sitechecker projects and their IDs.

Choose a project from the response, then ask:

For this project, compare GSC clicks and impressions for the last seven finalized days with the preceding seven days. Show both periods and the changes.

If the connection does not work

• If codex is not found, install the CLI and reopen your terminal.
• Check the saved server address with codex mcp get sitechecker.
• If authentication is required, run codex mcp login sitechecker.
• If a project is missing, confirm that you authorized the correct Sitechecker account.

For help, contact support@sitechecker.pro.