September 23, 2026

MCP server: AEOTrack in Claude Desktop, Cursor and other assistants

What it does

The AEOTrack MCP server lets Claude Desktop, Cursor or any other client that speaks the Model Context Protocol ask your account questions in plain language — "how visible is acme.com in AI answers?", "which sites does ChatGPT cite instead of us?", "track 'best CRM for startups' and check it now". Everything goes over HTTPS to the public API with your own API key; the server holds no data and has no database access.

It needs the Agency or Enterprise plan (the mcp_access capability). The API checks the plan on every call, so a key from a plan without it gets a 402 with the upgrade sentence, which the assistant relays. Integrations → MCP server in the app shows the same set-up, with your key filled in and the tools listed.

The seven tools

Tool	What it does	Spends
`list_domains`	Websites on the account, with their `domain_id`	–
`get_score(domain_id)`	AEO and GEO score, mention rate, confidence interval, engine coverage	–
`list_questions(domain_id, include_snippets=false)`	Every tracked question with per-engine verdicts	–
`add_question(domain_id, question)`	Track a new question (the plan's prompt ceiling applies)	–
`run_check(domain_id, query_id)`	Ask every engine now; 24-hour cooldown per question	One on-demand re-check from the monthly pool (the first check of a question is free)
`get_sources(domain_id)`	Most-cited source domains and your website's own cited URLs	–
`get_share_of_voice(domain_id)`	Mentions against named competitors, last 30 days	–

Install

The server is the mcp_server package of the AEOTrack backend repository and runs on Python:

cd aeo-v3-backend
pip install -r requirements-mcp.txt

Run it directly to check it starts: python -m mcp_server. It waits on stdin — that is the stdio transport working; Ctrl-C to stop.

Create an API key under Settings → Company → API keys (owners and admins; the key is shown once and starts with aeo_live_ — see The public API and API keys). Two environment variables configure the server:

Variable	Value
`AEOTRACK_API_KEY`	the key (`aeo_live_…`)
`AEOTRACK_API_URL`	the API origin; default `https://api.aeotrack.io`

Claude Desktop

Add the server to claude_desktop_config.json (Claude Desktop → Settings → Developer → Edit Config), then restart Claude:

{
  "mcpServers": {
    "aeotrack": {
      "command": "python",
      "args": ["-m", "mcp_server"],
      "cwd": "/path/to/aeo-v3-backend",
      "env": {
        "AEOTRACK_API_KEY": "aeo_live_xxxxxxxxxxxxxxxx",
        "AEOTRACK_API_URL": "https://api.aeotrack.io"
      }
    }
  }
}

On Windows use the full path to the interpreter that has the requirements installed, for example "command": "C:\\path\\to\\aeo-v3-backend\\venv\\Scripts\\python.exe".

Cursor

Put the same block in .cursor/mcp.json in the project, or in the global file under Cursor → Settings → MCP:

{
  "mcpServers": {
    "aeotrack": {
      "command": "python",
      "args": ["-m", "mcp_server"],
      "cwd": "/path/to/aeo-v3-backend",
      "env": {
        "AEOTRACK_API_KEY": "aeo_live_xxxxxxxxxxxxxxxx",
        "AEOTRACK_API_URL": "https://api.aeotrack.io"
      }
    }
  }
}

Things to know

The key is sent as X-API-Key. Never paste it into a prompt.
run_check asks all the engines for real and can take one to two minutes; the client timeout is 180 seconds.
Rate limit: 120 API calls per minute per key, the same as the public API. A chat that loops over every question on every site will hit it — ask for the summary first.
Revoking the key under Settings stops the server on its next call.