EzStats MCP
Query privacy-first ezStats website analytics, SEO signals, and goals from your coding agent without opening a separate dashboard.
Overview
io.ezstats/ezstats-mcp is a MCP server for the Grow phase that exposes privacy-first ezStats analytics, SEO, goals, and related tools to your agent via stdio or SSE.
What is this MCP server?
- npm package @ezstats/ezstats-mcp 0.2.1 with stdio transport plus remote SSE at go.ezstats.io/mcp/sse
- Privacy-first website analytics, SEO, goals, and related MCP tools
- Requires EZSTATS_API_KEY (secret) and optional EZSTATS_API_URL for Agent API base
- Dual transport: local stdio for Claude Code workflows and hosted SSE for remote clients
- Registry title ezStats MCP, schema 2025-12-11
- Package and server version 0.2.1
- Two transports: npm stdio (@ezstats/ezstats-mcp) and SSE remote at go.ezstats.io/mcp/sse
- Required secret env var EZSTATS_API_KEY documented in server manifest
What problem does it solve?
You run ezStats on your site but constantly context-switching to dashboards makes it hard to tie metrics to the content and funnel changes you are making in the agent.
Who is it for?
Solo builders using ezStats who want privacy-friendly site metrics and SEO context inside Claude Code, Cursor, or Codex.
Skip if: Teams standardized on Google Analytics 4 only with no ezStats account, or builders who need mobile app attribution rather than web analytics.
What do I get? / Deliverables
After installing @ezstats/ezstats-mcp and setting EZSTATS_API_KEY, your agent can query analytics, SEO, and goals so growth decisions stay in the same thread as your edits.
- Agent-queryable ezStats analytics snapshots
- SEO and goal metrics usable in growth prompts
- Configured stdio or SSE MCP connection to ezStats
Recommended MCP Servers
Journey fit
After ship and launch, solo builders need traffic and conversion visibility to decide what to fix, promote, or kill—analytics is the grow-phase feedback loop. Analytics subphase is the canonical home for MCP tools that read metrics, funnels, and SEO performance from your production site.
How it compares
ezStats analytics MCP bridge, not a full product analytics warehouse or ad network connector.
Common Questions / FAQ
Who is io.ezstats/ezstats-mcp for?
Indie developers and small teams on ezStats who want MCP access to web analytics, SEO, and goal tracking from their coding agent.
When should I use io.ezstats/ezstats-mcp?
Use it in grow and iterate loops when you are evaluating traffic, SEO performance, or goal conversions after launch and need answers without leaving the agent.
How do I add io.ezstats/ezstats-mcp to my agent?
Install @ezstats/ezstats-mcp from npm for stdio, set EZSTATS_API_KEY and optionally EZSTATS_API_URL, or register the SSE remote https://go.ezstats.io/mcp/sse per your client’s remote MCP support.