Documentation

The PulseTrack MCP server

Ask your analytics from the AI assistant you already use. One address, one sign-in to your account, and the assistant reads your numbers — without ever being able to change them.

Server address

https://pulsetrack.eu/api/mcp

Connecting

The server speaks MCP over Streamable HTTP. Any compatible assistant can connect; with most of them, three steps are enough:

  1. Add a custom MCP connector in your assistant and paste the address above.
  2. Sign in to your PulseTrack account when the assistant asks.
  3. Pick the site to authorize, then click Allow.

From the command line

# Claude Code
claude mcp add --transport http pulsetrack https://pulsetrack.eu/api/mcp

# Codex
codex mcp add pulsetrack --url https://pulsetrack.eu/api/mcp
codex mcp login pulsetrack

# Gemini CLI
gemini mcp add --transport http pulsetrack https://pulsetrack.eu/api/mcp

With an API key

For a script or a tool without a sign-in screen, generate a key in Settings → API access and send it in the Authorization: Bearer <key> header, or X-API-Key: <key>.

Once signed in to PulseTrack, Settings → API access walks through each tool step by step: Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code, Gemini CLI, Gemini, Notion, Copilot Studio and Le Chat.

Authentication and access

  • OAuth 2.1 with PKCE. Applications identify themselves with a published Client ID Metadata Document or through dynamic client registration (RFC 7591).
  • Access covers a single site, chosen on the consent screen. The assistant never sees your password.
  • Every connection can be revoked at any time from Settings → API access.
  • The MCP server comes with API access, on the Growth and Business plans.

Tools

Fifteen tools, all read-only. Each carries the readOnlyHint annotation, which assistants use to decide when to ask for confirmation.

Overview

get_statsVisitors, pageviews, bounce rate, pages, sources, countries and devices over 7, 30 or 90 days.Read-only
get_realtimeVisitors active in the last 5 minutes, and the pages they are on.Read-only
get_revenueStripe revenue tied to sources and landing pages, and recent transactions without customer e-mails.Read-only

Analysis

list_eventsThe custom events tracked and their properties, to build exact queries.Read-only
query_insightsThe Insights engine: measures, breakdowns, filters, formulas and period comparison.Read-only
list_funnelsThe configured funnels and their steps.Read-only
get_funnelConversion and drop-off at each step of a funnel.Read-only
get_retentionCohort retention of identified people, with the rate per period.Read-only
get_flowsPage-to-page flows, step by step.Read-only

Dashboards

list_boardsThe saved dashboards.Read-only
get_boardOne dashboard and its tiles, with each tile's query.Read-only

Product

list_experimentsA/B tests and their results: rate, lift, significance, sample needed.Read-only
list_feature_flagsFeature flags, their state and rollout percentage.Read-only

Accounts and sessions

list_groupsAccounts declared with group(): people, sessions, events, revenue. Aggregates only.Read-only
list_session_replaysRecorded sessions: page, device, duration, rage clicks, link to the dashboard.Read-only

Example prompts

  • "How many visitors and pageviews this week, and which sources grew the most compared with last week?"
  • "What is the checkout_completed over sessions conversion rate, week by week, over the last 30 days?"
  • "At which step of my signup funnel am I losing the most people?"
  • "Does my pricing page A/B test have a statistically significant winner?"
  • "Which traffic sources bring in the most revenue this month?"

Data and privacy

  • Read-only: the assistant cannot create, edit or delete anything.
  • No e-mail address or personal identifier is sent: answers are aggregates.
  • Anonymous visitors are counted per day, with an identifier that changes daily: one visitor back on three days counts three times over the period.
  • What the assistant receives is then handled by its vendor (Anthropic, OpenAI, Google, Microsoft, Mistral…) under their own terms.

Limits

  • 60 requests per minute per key or connection, shared with the REST API.
  • Time windows from 24 hours to 365 days depending on the tool.
  • Revenue needs a Stripe connection, and recorded sessions a plan with session replay; without them, the tool says so rather than returning zero.

MCP frequently asked questions →

Find out which channel actually pays.

Create a free accountCompare plans
Free forever tierNo credit card60-second setup