Sentry MCP vs Hyperping
A side-by-side look at the Sentry MCP and Hyperping MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sentry MCP for monitoring work as a local process; choose Hyperping for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Hyperping when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_monitors, get_monitor, create_monitor.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | SENTRY_ACCESS_TOKENEMBEDDED_AGENT_PROVIDEROPENAI_API_KEYANTHROPIC_API_KEYOPENROUTER_API_KEYOPENROUTER_MODELOPENROUTER_REASONING_EFFORTSENTRY_HOST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 938 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 69 |
| Full listing | View Sentry MCP | View Hyperping |
Tools & capabilities
Sentry MCP tools
No tool names declared yet. Check the project README from the listing page.
Hyperping tools 69
list_monitorsPaginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).get_monitorFetch a single monitor by its UUID.create_monitorCreate a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.update_monitorPatch a monitor. Pass only fields you want to change; others are preserved.pause_monitorPause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.resume_monitorResume a paused monitor. Same as update_monitor with paused=false.search_monitors_by_nameCase-insensitive substring search across monitor names and URLs.get_status_summaryUp/down/paused counts plus a list of currently down monitors with the timestamp they went down.list_outagesPaginated list of outages in the project. Filter by status, type, or search term.get_outageFetch a single outage by UUID, including acknowledgements, description, and root cause.get_outage_timelineFull activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.get_monitor_outagesPaginated list of outages scoped to one monitor. Convenience wrapper around list_outages.- +57 more on 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.
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"
}
}
}
}
Hyperping
{
"mcpServers": {
"hyperping": {
"url": "https://api.hyperping.io/v1/mcp"
}
}
}
Frequently asked questions
Sentry MCP is categorized under Monitoring and uses a local stdio subprocess. Hyperping belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Sentry MCP for monitoring work and Hyperping 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.
Sentry MCP is listed as free. Auth: api key required. Hyperping has no declared pricing — check the project's own site. 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 getsentry-sentry-mcp and hyperping as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sentry MCP has a quality signal of 55/100 (Good) with 6 views, 0 installs and 938 GitHub stars. Hyperping has 56/100 (Good) with 2 views, 0 installs and 1 GitHub stars.