Trackela

Model Context Protocol

Analytics your agent can actually query.

Connect Trackela to Cursor, Claude Code, or Codex. Same data as the dashboard — traffic, revenue, visitors, live — without clicking around.

https://trackela.com/api/mcp

01

Create a token

Sign in → any website → Settings → MCP. Name the token (Cursor, Claude, Codex) and copy it once. It starts with trk_.

02

Add the server

Paste the config into your client. Every request uses Authorization: Bearer trk_… against the Streamable HTTP endpoint.

03

Ask in English

“Who converted from the blog today?” “Which source makes the most revenue?” The agent calls Trackela tools — not your database.

Client snippets

Replace trk_your_token_here with the token from Settings → MCP.

Cursor / Claude Desktop

{
  "mcpServers": {
    "trackela": {
      "url": "https://trackela.com/api/mcp",
      "headers": {
        "Authorization": "Bearer trk_your_token_here"
      }
    }
  }
}

Claude Code

claude mcp add --transport http trackela https://trackela.com/api/mcp \
  --header "Authorization: Bearer trk_xxx"

Codex

export TRACKELA_TOKEN=trk_xxx

codex mcp add trackela \
  --url https://trackela.com/api/mcp \
  --bearer-token-env-var TRACKELA_TOKEN

stdio clients (mcp-remote)

{
  "mcpServers": {
    "trackela": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://trackela.com/api/mcp",
        "--header",
        "Authorization: Bearer trk_your_token_here"
      ]
    }
  }
}

Tools

Read-only. website_id accepts the UUID or public id (site_…). Omit it if you only have one website.

  • trackela_websites_list

    List websites this token can access (id, public id, name, domain).

  • trackela_analytics_overview

    Overview metrics: visitors, sessions, pageviews, signups, customers, revenue, bounce rate, avg time, and deltas vs the previous period.

  • trackela_analytics_timeseries

    Daily or hourly timeseries of visitors, conversions, and revenue.

  • trackela_analytics_sources

    Traffic sources ranked by visitors, with signups, customers, and attributed revenue.

  • trackela_analytics_pages

    Top pages with pageviews, unique visitors, conversions, and revenue.

  • trackela_analytics_breakdown

    Break sessions down by country, device, browser, OS, city, campaign, channel, referrer, or landing page.

  • trackela_analytics_revenue

    Revenue attributed by source (customers, visitors, revenue per visitor).

  • trackela_analytics_live

    Visitors active right now (path, source, country, device).

  • trackela_visitors_list

    Recent visitors with source, geo, device, bounce, time on site, and revenue. Search by email or visitor id.

  • trackela_visitors_journey

    Full event journey for one visitor (pages, events, acquisition, payments).

  • trackela_insights_list

    Current growth insights and opportunities for a website (not dismissed).

Safety

  • Tokens are hashed at rest and shown once.
  • Every call checks membership — the agent only sees your sites.
  • No delete-website, no payment connect, no minting extra tokens from MCP.
  • Revoke a token anytime in Settings → MCP.