What is an analytics MCP server?
An analytics MCP server lets your agent read your site's visits and answer questions about them. What it is, what it can do and how to connect one.
Updated
An analytics MCP server is web analytics your agent reads through the Model Context Protocol (MCP). Instead of opening a dashboard, you ask Claude, Cursor or Codex "What changed on the site this week?", and the agent calls the server's tools, reads the numbers and answers with them.
nextanalytica is one: a remote MCP server at https://mcp.nextanalytica.app/mcp, with a tag that collects your site's visits.
How is it different from a dashboard?
A dashboard shows the charts someone chose in advance. An agent with an analytics MCP server asks the question you have now, follows up on its own (which page, which channel, since when) and explains the answer in a sentence. It can also read your team's goals and decisions, so the answer fits your business.
What can your agent do with it?
- Read visits, pages, channels and conversions by day with
queryandget_dashboard. - Find what changed and why with
find_changesandget_timeline. - Read the signals our daily rules found with
list_insights. - Look at people and cohorts with
find_peopleandget_person. - Add the tag to your site with
get_tag.
Every tool is listed in the MCP tools reference.
Does it run on a schedule?
Yes. Skills are instructions your agent runs for you on a schedule, on your own Claude Code once you allow it. They write a finding only when something is worth your time. See Skills.
How do I connect one?
Add the address to your agent and sign in. In Claude Code:
claude mcp add --transport http nextanalytica https://mcp.nextanalytica.app/mcpOther clients: Claude Desktop, Cursor, Codex and more.