MCP Server

Connect any MCP-compatible AI client to Trackee's hosted MCP server and get one tool per API endpoint.

Trackee runs a hosted MCP (Model Context Protocol) server at https://mcp.trackee.dev/mcp. Add one URL to your AI client and it gets a tool for every Trackee endpoint: rankings, AI visibility, keywords, mentions, competitors, and brand management.

Nothing to install. Nothing running locally.

What's MCP?

Model Context Protocol is an open standard from Anthropic for letting AI assistants call external tools. When you add Trackee's MCP server to a compatible client, the AI can check rankings, ask whether models mention your brand, pull keyword data, and manage brands directly.

Connect your AI client

You will need a Trackee access key. Grab one from the dashboard.

Claude.ai (web)

In Claude, go to Customize → Connectors → Add custom connector, then paste this URL into the Remote MCP field:

https://mcp.trackee.dev/mcp?access_key=YOUR_TRACKEE_API_KEY

Replace YOUR_TRACKEE_API_KEY with your access key from the dashboard.

Claude Desktop / Claude Code / Cursor

Add the following to your MCP config:

claude_desktop_config.json / .cursor/mcp.json

{
  "mcpServers": {
    "trackee": {
      "url": "https://mcp.trackee.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TRACKEE_API_KEY"
      }
    }
  }
}

Restart the client. Trackee's tools (get_visibility, get_rank, get_competitors, and more) will appear in the available-tools list.

ChatGPT and other Streamable-HTTP MCP clients

Same shape. Point the client at https://mcp.trackee.dev/mcp and pass Authorization: Bearer YOUR_TRACKEE_API_KEY. If your client does not support custom headers, append ?access_key=YOUR_TRACKEE_API_KEY to the URL instead.

Available tools

The MCP server exposes one tool per public API operation.

Tool	What it does
`get_visibility`	Check if ChatGPT, Claude, Gemini, or Perplexity mention a brand
`get_rank`	Google position and AI Overview presence for a keyword
`get_keyword_volume`	Search volume, CPC, and competition for keywords
`get_mentions`	Web pages that mention a brand for a query
`get_competitors`	Domains competing for a set of keywords
`create_brand` / `list_brands` / `get_brand` / `update_brand` / `delete_brand`	Manage the brands you track (free)
`set_brand_prompts` / `set_brand_competitors`	Set a brand's tracked prompts and competitors (free)
`get_usage`	Credit balance and usage history (free)
`api_health`	Check that the API is up (free)

Try it

Once connected, ask your AI client things like:

"Does ChatGPT mention Salesforce when asked for the best CRM software?"
"Where does salesforce.com rank for best crm software, and is it in the AI Overview?"
"What is the monthly search volume for crm software and email marketing?"
"Who are the top domains competing for best crm?"
"What is my Trackee credit balance?"

The AI calls the relevant tools, Trackee runs the checks, and you get structured results back inline.

Authentication

The MCP server accepts your access key three ways (priority order):

Authorization: Bearer <key> — recommended.
x-access-key: <key> — the same header the REST API uses.
?access_key=<key> query string — for clients without custom-header support.

The MCP server forwards every call to api.trackee.dev, which handles auth, credits, and rate limiting. So credit usage, plan limits, and access-key permissions behave exactly like the REST API. Reads such as get_usage, api_health, and brand management never cost credits.

Troubleshooting

401 Unauthorized — your access key is missing or invalid. Confirm the Bearer token is set in the client config and that the key works against the REST API.
402 Payment Required — you are out of credits for a paid check. Top up or wait for your cycle to reset.
429 Too Many Requests — you hit your plan's rate limit. Space the calls out or upgrade.
Tools do not appear in the client — restart the AI client after editing the config. Some clients also need MCP enabled explicitly in settings.

On this page