A website analytics MCP server: ask your agent about your traffic

The Model Context Protocol (MCP) lets a coding agent call tools on a server. An analytics MCP server turns your traffic into tools the agent can call, so instead of opening a dashboard you ask "why did traffic jump on Tuesday?" and the agent fetches the numbers itself.

What the agent can do

• Read traffic: overview with change against the previous period, time series, top sources, pages, countries, browsers and systems.
• Answer questions about visits: count pageviews or events and visitors for any mix of country, browser, system, source, page and event, grouped by day, hour or any of those.
• Explain spikes: find traffic jumps and rank the sources, pages and events behind each one.
• Follow visitors through steps: create and read funnels to see where people drop off.
• Plan and measure marketing: channels ranked by conversions, ranked growth actions, tracked links for everything it publishes, and results per campaign.

Connect it in two minutes

With agentlytics the fastest route is one sentence. Your agent reads the setup instructions, asks for your email and domain, signs you in with a six-digit code, adds the script to your project and connects itself.

To connect by hand in Claude Code, add the server with your site's read key:

claude mcp add --scope user --transport http agentlytics https://a.measuremy.site/mcp --header "Authorization: Bearer YOUR_READ_KEY"

Cursor and Codex use a short config file instead. The agent guide has each one.

Questions that work well

• "How many iOS visitors from the US came last week, and where do my Firefox users live?"
• "Which channel actually brings signups?"
• "Where do visitors drop off between the homepage and signup?"
• "I'm posting on Reddit tomorrow. Write the post and give me a tracked link."

What it can and can't do

Each read key is scoped to one site. The agent can read analytics and create tracked links, annotations, funnels and a public dashboard when you ask. It can't change your account or billing, and it never sees IP addresses or browser identification strings, because they aren't stored.

More guides

• Add website analytics to your project with Claude Code
• Find out why your website traffic spiked
• Track clicks and find where visitors drop off, without writing code
• Cookieless analytics: how it works, and what you give up
• A simpler Google Analytics alternative for developers