Every agent that can read your numbers
Alexander runs one MCP server. Anything that speaks the protocol can ask it a question in words, and the key it asks with reads exactly one site and nothing else.
POSThttps://mcp.alxndr.ai/mcp
Assistants
12 clientsChat, where the question is a sentence and the answer goes into the work.
ChatGPT
Add Alexander as a connector and ask it in the same thread as everything else.
In Settings, Connectors
Claude
Answer from your real numbers instead of guessing at them.
In Settings, Developer
Claude Cowork
Put the numbers in the room where the work is being decided.
In Customize, Connectors
OpenClaw
Message the agent and it reads your analytics back to you.
In Settings, MCP
Hermes Agent
An agent that can pull the numbers while it works on something else.
In the MCP config
Grok Bot
Ask it in the feed, get the figure from your own site.
By asking the Bot
DeepSeek
Reasoning over your own rows instead of a guess.
In the MCP configuration
Kimi K3
A long context, filled with your own numbers.
In the MCP configuration
Muse
Ask what happened, and get the sentence rather than the chart.
In the MCP configuration
Perplexity Computer
Research your own site with the same tool you research everything else.
In Connectors
LibreChat
Self-hosted chat, with your analytics as a tool.
In librechat.yaml
Raycast
Ask from the launcher, without opening anything.
In Manage MCP Servers
Editors
7 clientsThe window the change is made in, reading what the page does today.
Cursor
The editor about to change the page can read what the page does.
In .cursor/mcp.json
Grok Build
Build against what the page actually does.
In the terminal
GitHub Copilot
Agent mode in VS Code, pointed at your own numbers.
In .vscode/mcp.json
Windsurf
Cascade can pull the traffic behind the file it is looking at.
In the Windsurf MCP config
Zed
A context server in Zed's assistant panel.
In Zed's settings
Cline
The VS Code agent that asks before it acts.
In cline_mcp_settings.json
Continue
Open source, in VS Code and JetBrains.
In ~/.continue/config.yaml
Terminals
6 clientsCommand line agents, already in the repository that caused the number.
Claude Code
Ask your analytics a question from the terminal you are already in.
In the project directory
Codex
OpenAI's terminal agent, reading your traffic while it edits.
In ~/.codex/config.toml
Gemini
Google's terminal agent, with your analytics as one of its tools.
In ~/.gemini/settings.json
nanoclaw
Small, local, and pointed at your own analytics.
In the config file
AI Agents CLI
Any terminal agent, pointed at the same server.
In the agent's config
Goose
Block's open source agent, on the desktop or in a terminal.
In Settings, Extensions
Automation
3 clientsNo window at all. The question gets asked on a schedule.
Five tools. That is the whole of it.
Whichever client you pick above, this is what it reaches. Read only, one site, no sixth tool hiding behind the list.
Headline numbers
get_overview
Visitors, pageviews, revenue, conversions, bounce rate and who is on the site this second.
Sources
get_sources
Where visitors came from, ranked by revenue per visitor rather than by volume.
Pages
get_pages
The most viewed pages, each with the revenue of the sessions that saw it.
Funnel
get_funnel
Every step with the drop-off to the next, so the leak has a name.
Insights
get_insights
The written findings: what changed, the evidence, the suggested action, a confidence score.
Your numbers, in whichever window is already open
Add the tracker, issue a key, paste it into the client you use. The whole of it takes about a minute, and the first question answers itself.
10,000 events a month on the free plan, no card, and the tracker is one line.