ezStats MCP

io.ezstatsPublished by ezstats.ioOfficial publisherv0.2.1Updated Oct 25, 2026

Privacy-first website analytics MCP server for ezStats with analytics, SEO, goals, and MCP tools.

VerifiedSSEWeb executableData & Analytics

Overview

AI-generated overview

Privacy-first website analytics MCP server for ezStats, letting an assistant work with analytics, SEO and goal data through ezStats tools.

What you can do
Work with website analytics data from ezStats, including traffic and reporting figures, through the server's MCP tools (the manifest lists no individual tools). Query SEO-related information for a site. Access goal data configured in ezStats. Connect either to the hosted remote endpoint or run the npm package locally over stdio.
When to use it
Useful when you want an assistant to pull ezStats website analytics, SEO and goal information into a conversation or workflow without leaving the chat, especially for privacy-conscious sites tracked with ezStats.
Requirements
An ezStats account and API key supplied through the EZSTATS_API_KEY environment variable. Optionally set EZSTATS_API_URL to point at a different ezStats Agent API base URL. Either the remote endpoint or the npm package @ezstats/ezstats-mcp run locally with Node.js, plus network access to ezStats.
Before you install
The server requires an ezStats API key, which is a secret; keep it out of shared configuration and logs. It exposes website analytics, SEO and goal data, which may be business-sensitive, to the assistant and to the model provider. The manifest lists no write tools, but confirm what the tools can change before relying on it.

Installation

In SourceWeft

  1. Open ezStats MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.ezstats%2Fezstats-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ezstats": {
      "type": "sse",
      "url": "https://go.ezstats.io/mcp/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.