Ezstat MCP Server vs Sentry MCP
A side-by-side look at the Ezstat MCP Server and Sentry MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ezstat MCP Server for monitoring work over a hosted endpoint; choose Sentry MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ezstat MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
EZSTAT_API_KEY. - You want tools like
track_metric, ask_ezstat, read_stat.
Choose Sentry MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SENTRY_ACCESS_TOKEN, EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY, OPENROUTER_MODEL, OPENROUTER_REASONING_EFFORT, SENTRY_HOST.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | EZSTAT_API_KEY | SENTRY_ACCESS_TOKENEMBEDDED_AGENT_PROVIDEROPENAI_API_KEYANTHROPIC_API_KEYOPENROUTER_API_KEYOPENROUTER_MODELOPENROUTER_REASONING_EFFORTSENTRY_HOST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 938 |
| Directory activity | 3 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View Ezstat MCP Server | View Sentry MCP |
Tools & capabilities
Ezstat MCP Server tools 7
track_metricRecord a metric point your app "produced". Use this whenever the surrounding code emits a counter or gauge — e.g. on a page view, a successful checkout, or a measured latency. Counters are +N (default +1), values are gauges (e.g. 42.5 ms).ask_ezstatAsk a natural-language question about the account's metrics. This is the agent-read path: send a question like "what spiked yesterday?" or "compare signups vs cancellations last 7 days" and EzStat returns a grounded answer plus the underlying data it used.read_statRead a single stat: latest value, recent series, and basic summary (count/min/max/avg/sum). Use this for a structured read of one metric — prefer `ask_ezstat` for free-form questions over many stats.list_statsList the account's metrics — names and types. Call this first when you don't know what stats exist in the account.create_alertCreate an alert on a stat: webhook fires when the condition is met (above/below threshold, % change, heartbeat/missing data, sustained). Deliveries retry with backoff and carry a stable idempotency_key so receivers can dedup. The stat is referenced by NAME; it must already exist.list_alertsList the account's alerts: id, stat, condition, channel, enabled, last trigger time.delete_alertDelete an alert by id (see list_alerts).
Sentry MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ezstat MCP Server
{
"mcpServers": {
"ezstat-mcp-server": {
"url": "https://mcp.ezstat.dev"
}
}
}
Sentry MCP
{
"mcpServers": {
"getsentry-sentry-mcp": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server@latest"
],
"env": {
"SENTRY_ACCESS_TOKEN": "YOUR_SENTRY_ACCESS_TOKEN_HERE",
"EMBEDDED_AGENT_PROVIDER": "YOUR_EMBEDDED_AGENT_PROVIDER_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"OPENROUTER_MODEL": "YOUR_OPENROUTER_MODEL_HERE",
"OPENROUTER_REASONING_EFFORT": "YOUR_OPENROUTER_REASONING_EFFORT_HERE",
"SENTRY_HOST": "YOUR_SENTRY_HOST_HERE"
}
}
}
}
Frequently asked questions
Ezstat MCP Server is categorized under Monitoring and uses a remote HTTP/SSE transport. Sentry MCP belongs to Monitoring and uses a local stdio subprocess. Pick Ezstat MCP Server for monitoring work and Sentry MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ezstat MCP Server has no declared pricing — check the project's own site. Sentry MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ezstat-mcp-server and getsentry-sentry-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ezstat MCP Server has a quality signal of 55/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Sentry MCP has 55/100 (Good) with 6 views, 0 installs and 938 GitHub stars.