Agent setup

Connect Claude Code, Codex or Cursor to the app. The address, the password, the 33 tools and 6 ready-made task templates, and which ones use up Google quota.

This guide connects your AI assistant to the app and runs its first command. Once connected, you can say "audit the site and write a report". The assistant reads Search Console data, runs the audit and saves the report in the Reports screen. This connection is called an assistant connection (MCP); it lets the assistant call the app's tools (for example list_projects). Connecting is optional, and the app is complete without it.

What you need

• A running app and a project connected to Search Console.
• One of Claude Code, Codex, Cursor, VS Code Copilot or Gemini CLI. The app gives ready-made setup text for the first three.
• The Agent setup screen in the app. It is in the left menu, under Agent.

Steps

1. Open the Agent setup screen. The badge at the top says Not connected yet or Connected. If connected, it also shows text like "Claude Code, last call 2 min ago". Below it you see the connection address and a copy button: http://127.0.0.1:3001/mcp (localhost on Docker).
2. Find the password. The app protects the connection against unauthorized calls with a password, which is not shown on screen. In the Windows package, the password is in the mcp-token file in the data folder. From the taskbar menu, choose Open data folder. On Docker, run this command: docker compose exec -T seotracker cat /app/.wrangler/mcp-token (in Git Bash, put MSYS_NO_PATHCONV=1 in front).
3. Follow the section for your assistant.

Claude Code

In the terminal (the command window), run the following. Replace <parola> with your own password:

claude mcp add --transport http --scope user seotracker http://127.0.0.1:3001/mcp --header "Authorization: Bearer <parola>"

Then type /mcp inside Claude Code and choose Reconnect. Call the ready-made task templates with a slash, for example /seo-audit.

Codex

Run this command:

codex mcp add seotracker --url http://127.0.0.1:3001/mcp --bearer-token-env-var SEOTRACKER_MCP_AUTH

Then put the password in an environment variable (a setting your computer remembers) named SEOTRACKER_MCP_AUTH. On Windows, with PowerShell: [Environment]::SetEnvironmentVariable('SEOTRACKER_MCP_AUTH', '<parola>', 'User'). Call the templates like $seo-audit.

Cursor

Write this in the .cursor/mcp.json file in your project:

{
  "mcpServers": {
    "seotracker": {
      "url": "http://127.0.0.1:3001/mcp",
      "headers": { "Authorization": "Bearer ${env:SEOTRACKER_MCP_AUTH}" }
    }
  }
}

Set the environment variable the same way as for Codex. This setup has not been tried on a Cursor installation yet. If your Cursor version asks for a different field, check Cursor's documentation.

Ready-made setup text

This is the easier route. First, copy the text:

1. Press the Ajan kurulum istemini kopyala (Copy agent setup prompt) button on the screen. There is a separate button for Codex.
2. Paste the text into your assistant. The assistant sets up the connection, tests it with "whoami" and "list_projects", and installs the templates.

The setup prompt (the full setup) has the assistant do the whole setup for you, from getting the app running to the Google connection. It knows both the Windows package and the Docker setup.

Installing the ready-made task templates

The Skills tab describes the six ready-made task templates. Tell the assistant "install the seotracker skills". The setup text knows where to copy them. To update, press the Güncelleme istemini kopyala (Copy update prompt) button.

Tools

There are 33 tools in total. The "Writes" column shows the tools that change data in the app. The "Quota" column shows the tools that use up Google's daily allowance. Do not let the assistant call a tool that writes without your approval. Well-built templates ask you first, but the app does not.

The Analytics tools use Google's Analytics report allowance (200,000 units a day on a standard property). You can follow this allowance in the app, in the Limits section of the Settings screen.

Ready-made task templates (skills)

Check

• Tell the assistant "call the whoami tool". It should tell you the installation ID.
• The badge on the Agent setup screen should say Connected, and the time of the last call should show.
• "list_projects" should list your projects.

Frequently asked questions

Does the assistant send my data outside? Your data goes to whichever model the assistant uses. That depends on the assistant's own privacy terms. The app itself only answers connections on your computer.

Does it work without a password? On Docker it works with MCP_TOKEN=off. In the Windows package the password is always on. On a connection without a password, any program on the same computer can call the 33 tools.

Can the assistant use up my Google allowance? inspect_urls and run_site_audit use it. The templates ask about at most 20 addresses per task. They start an audit only when you ask. Set the same limit for any other assistant.

Which assistant is better? It makes no difference; the tools are the same. The setup text is ready for Claude Code, Codex and Cursor. Other assistants work with the same address and password if they support MCP.

If something goes wrong

• The assistant gets a 401 error. The password is wrong or is not being sent. Copy the value from the file again. Make sure no line break is left at the end.
• The connection is refused. The app is not running. Check the taskbar icon, or the output of docker compose ps.
• The assistant says "tool not found". Reload the connection. In Claude Code, type /mcp and choose Reconnect.
• The templates do not show up. Paste the setup text again. The templates are copied into the assistant's own folder ($HOME/.agents/skills in Codex).

Last updated: October 24, 2026. Spotted a mistake? Report it on GitHub.