Ezstat MCP server
{
"mcpServers": {
"ezstat": {
"type": "http",
"url": "https://mcp.ezstat.dev"
}
}
}{
"mcpServers": {
"ezstat": {
"type": "http",
"url": "https://mcp.ezstat.dev"
}
}
}{
"mcpServers": {
"ezstat": {
"type": "http",
"url": "https://mcp.ezstat.dev"
}
}
}{
"servers": {
"ezstat": {
"type": "http",
"url": "https://mcp.ezstat.dev"
}
}
}{
"mcpServers": {
"ezstat": {
"type": "http",
"url": "https://mcp.ezstat.dev"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y ezstat-mcp-serverversion 0.7.0
What it does
An MCP server for EzStat, a hosted metrics service. It lets Claude, Cursor, and other MCP agents push metrics, query them in natural language, and manage alerts—all without leaving the agent interface. Available as a local stdio server or a hosted HTTP endpoint.
- Record application metrics (counters and gauges) directly from agent code without manual dashboard interaction.
- Ask natural-language questions about your metrics and get structured summaries (min/max/avg/sum) for a time window.
- Create and manage webhook alerts on metrics with threshold, percentage-change, heartbeat, or sustained-value conditions.
Tools this server exposes
| Tool | Does |
|---|---|
| track_metric | Record a metric point as a counter (increment by N, default +1) or gauge (e.g., a latency value). |
| ask_ezstat | Ask a natural-language question about your metrics. |
| read_stat | Retrieve the latest value, series data, and summary statistics (count/min/max/avg/sum) for a metric over a specified time window. |
| list_stats | List all metrics in the account with their names, types, and descriptions. |
| create_alert | Create a webhook alert on a metric with threshold, percentage-change, heartbeat, or sustained-value conditions. |
| list_alerts | List all alerts in the account, showing their id, stat, condition, channel, enabled status, and last fire time. |
| delete_alert | Delete an alert by its id. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.