Track and query EzStat metrics from Claude, Cursor, or any MCP agent. StatHat-compatible.
MCPpedia last refreshed this data
dev.ezstat/ezstat-mcp-server is an MCP server that track and query EzStat metrics from Claude, Cursor, or any MCP agent. StatHat-compatible. Its tool list has not been published yet over stdio and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"ezstat": {
"url": "https://mcp.ezstat.dev",
"type": "http",
"headers": {
"Authorization": "Bearer ezkey_your_api_key_here"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A standalone Model Context Protocol server for EzStat. Let Claude / Cursor / any MCP-compatible agent push and read your metrics natively — no copy-paste, no dashboard hop. This is the product behind the "metrics your agents write and read themselves" positioning: every agent that touches your code can also touch your observability.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'ezstat-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked ezstat-mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / analytics
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
An autonomous agent that conducts deep research on any data using any LLM providers
The official MCP server implementation for the Perplexity API Platform
1000+ scientific tools for AI scientists: life science, reserach, literature, and more.
MCP Security Weekly
Get CVE alerts and security updates for dev.ezstat/ezstat-mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A standalone Model Context Protocol server for EzStat. Let Claude / Cursor / any MCP-compatible agent push and read your metrics natively — no copy-paste, no dashboard hop. This is the product behind the "metrics your agents write and read themselves" positioning: every agent that touches your code can also touch your observability.
The server speaks stdio (the standard transport for local agent runners) and — as a
hosted endpoint at https://mcp.ezstat.dev — streamable HTTP, exposing the same
seven focused tools. Each tool description is written for an agent audience so the model
knows when to call it.
Agents can connect to the hosted streamable-HTTP endpoint with nothing but an EzStat API key — no npm install, no local process:
{
"mcpServers": {
"ezstat": {
"type": "http",
"url": "https://mcp.ezstat.dev",
"headers": {
"Authorization": "Bearer ezkey_your_api_key_here"
}
}
}
}
Authorization: Bearer <ezkey>;
the server holds no key of its own and each connection only ever sees its own account.initialize and tools/list work without a key, so clients and
registry inspectors can introspect the tool surface before you configure anything.This hosted endpoint also satisfies the requirements for hosted/remote listings on MCP
registries (e.g. Smithery's hosted-server path) — see server.json's remotes entry.
The stdio transport below remains fully supported and is still the right choice when you want the server running locally under your own runner.
| Tool | What it does |
|---|---|
track_metric | Record a metric point your app "produced" — counter (+N, default +1) or gauge (e.g. 42.5 ms). |
ask_ezstat | Ask a natural-language question about your metrics (the agent-read path). |
read_stat | Structured read of a stat: latest value + series + summary (count/min/max/avg/sum) for a window. |
list_stats | List the account's metrics (names + types + description). |
create_alert | Create a webhook alert on a stat (threshold / %-change / heartbeat / sustained). |
list_alerts | List the account's alerts (id, stat, condition, channel, enabled, last fire). |
delete_alert | Delete an alert by id. |
Tool descriptions are tuned for agent reasoning — see src/server.ts.
# pnpm
pnpm add -g ezstat-mcp-server
# npm
npm install -g ezstat-mcp-server
Claude Desktop (~/.config/Claude/claude_desktop_config.json on macOS/Linux,
%APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"ezstat": {
"command": "ezstat-mcp-server",
"env": {
"EZSTAT_API_KEY": "ezkey_your_api_key_here"
}
}
}
}
Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"ezstat": {
"command": "ezstat-mcp-server",
"env": {
"EZSTAT_API_KEY": "ezkey_your_api_key_here"
}
}
}
}
Get your API key from https://ezstat.dev (it's the "ezkey").
npx -y @s
... [View full README on GitHub](https://github.com/clira-dev/ezstat-mcp-server#readme)