Better Stack MCP by usefulapi
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Connect it
Settings → Connectors → Add custom connector
URL: https://betterstack.usefulapi.io/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://betterstack.usefulapi.io/mcp{
"mcpServers": {
"betterstack": {
"url": "https://betterstack.usefulapi.io/mcp"
}
}
}claude mcp add --transport http betterstack https://betterstack.usefulapi.io/mcp{
"servers": {
"betterstack": {
"type": "http",
"url": "https://betterstack.usefulapi.io/mcp"
}
}
}9 tools, verified live
list_monitorsread-onlyList uptime monitors with their status (up/down/paused/pending/maintenance/validating), check frequency, and alert settings. Good first call to discover what is being monitored. Uptime API: GET /api/v2/monitors.
get_monitorread-onlyGet a single monitor by id, including current status, last_checked_at, SSL/HTTP settings, regions, and alerting configuration. Uptime API: GET /api/v2/monitors/{id}.
list_incidentsread-onlyList incidents (alerts triggered by monitors/heartbeats), filterable by date range, monitor, and acknowledged/resolved state. Each incident carries cause, started_at, acknowledged_at, resolved_at. Uptime API: GET /api/v3/incidents.
get_incidentread-onlyGet a single incident by id, including cause, status, timeline timestamps (started/acknowledged/resolved), who acknowledged/resolved it, and the related monitor. Uptime API: GET /api/v3/incidents/{id}.
list_heartbeatsread-onlyList heartbeats (cron/background-job monitors that expect a periodic ping), with period, grace, and status (up/down/paused/pending). Uptime API: GET /api/v2/heartbeats.
list_on_callread-onlyList on-call calendars/schedules and the users currently on call for escalation. Useful to see who gets paged. Uptime API: GET /api/v2/on-calls.
list_status_pagesread-onlyList public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.
acknowledge_incidentAcknowledge an ongoing incident, signalling that someone is looking into it (stops further escalation). Idempotent-ish: acknowledging an already-acknowledged incident returns HTTP 409. Uptime API: POST /api/v3/incidents/{id}/acknowledge.
resolve_incidentResolve an ongoing incident, marking it as handled/closed. Idempotent-ish: resolving an already-resolved incident returns HTTP 409. Uptime API: POST /api/v3/incidents/{id}/resolve.
Alternatives in Cloud & Infra
Compare →FCFireCMS CloudA
Manage FireCMS Cloud from an AI agent: Firestore data, collections, schemas and users.
HAHydrata - ANUGA Flood SimulationA
Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
INInfraNodeA
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
DCDaedalMap CIA World FactbookA
CIA World Factbook country indicators: infrastructure, energy, demographics, economy, 2002-2026.
CCCypress Cloud MCPB
Direct access to Cypress tests results and accessibility reports in your AI workflow.
packagecloud MCP by usefulapiB
Read packagecloud repos, packages, versions and download stats; create repos, promote and delete.