Ezstat MCP Server

What ezstat-mcp-server MCP server does

ezstat-mcp-server MCP server gives an MCP-compatible agent access to an EzStat account’s metrics and alerts. It can record counter increments or gauge values, retrieve a structured view of one stat, and answer natural-language questions about metric data. It can also enumerate available stats and manage webhook alerts.

The server is designed for agent workflows that need both metric ingestion and metric inspection. For example, an agent can record a value after a task, inspect recent results, or ask EzStat a question about a metric window. Authentication is performed with an EzStat API key, so the available data belongs to the configured account.

How it works

The server supports two transports. A local process communicates over stdio, which fits MCP clients that start a command on the user’s machine. A hosted endpoint at https://mcp.ezstat.dev accepts streamable HTTP requests and uses the same seven tools. Hosted requests carry the account key in an Authorization: Bearer header; the endpoint does not keep a server-wide key and does not require sessions.

Tool calls map to EzStat API routes. track_metric posts to the ingest endpoint, while ask_ezstat, read_stat, and list_stats use query and stats endpoints. Alert tools create, list, and delete alerts associated with the account. The structured read includes the latest value, a series, and count, minimum, maximum, average, and sum for a requested window.

Setup and configuration

For local use, install the package globally with npm or pnpm, then configure the MCP client to run ezstat-mcp-server. Claude Desktop, Claude Code, and Cursor examples are provided in the project documentation. Set EZSTAT_API_KEY to the EzStat key issued by ezstat.dev; the key should not be hardcoded or logged.

The hosted option requires no package installation. Configure an HTTP MCP connection with the endpoint URL and an Authorization header containing the bearer key. Discovery operations such as initialization and tool listing can run without a key, but tool calls require a valid one.

Optional environment variables can override the EzStat base URL, request timeout, ingest path, query path, and stats-list path. The defaults target the public EzStat API, use a 10-second request timeout, and use the documented API routes.

Tools and capabilities

• track_metric: records a counter increment or gauge value.
• ask_ezstat: sends a natural-language metric question to EzStat.
• read_stat: returns a stat’s latest value, series, and summary values for a window.
• list_stats: lists metric names, types, and descriptions.
• create_alert: creates a webhook alert based on a threshold, percentage change, heartbeat, or sustained condition.
• list_alerts: returns alert identifiers, conditions, channels, enabled state, and last-fire information.
• delete_alert: removes an alert by ID.

Limitations and notes

The ezstat-mcp-server MCP server requires an EzStat API key for metric operations. The local transport requires a running local process, while the hosted transport depends on access to the remote endpoint. Hosted requests are stateless, so each request must include the necessary authentication.

The server exposes EzStat functionality; it does not provide an independent metrics store. Its optional URL and path settings are intended for staging, self-hosted, or proxied API deployments. Clients can inspect the tool surface without credentials, but that discovery does not grant access to account data.