AI-powered infrastructure monitoring — health, incidents, predictions, RCA, deploy safety
AI-powered infrastructure monitoring — health, incidents, predictions, RCA, deploy safety. The uptimebolt mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.
UptimeBolt is an AI-first monitoring platform that groups monitors into logical business services, predicts cascade failures before they happen, and automatically identifies which deploy caused each incident — including the commit, files, and lines of code responsible.
UptimeBolt is an AI-first SaaS monitoring platform for DevOps teams and SREs. Key capabilities:
Everything the assistant can do here goes through one of these:
get_service_status — Health status of business services with health score (0-100), monitor breakdown, and active incidentsget_monitors — List all monitors with operational status, response time, and uptime percentageget_monitor_health — Detailed health for a specific monitor including response time trends and active predictionsget_monitor_metrics — Response time stats (avg, p95, p99), uptime percentage, and error breakdownget_incidents — Active and resolved incidents with optional AI root cause analysis detailsget_predictions — AI predictions for upcoming issues with confidence levels and predicted impactget_deployments — Recent deployments with automatic incident correlation (GitHub/GitLab)run_root_cause_analysis — AI-powered RCA using multi-model analysis (Claude, GPT) with deploy correlationis_safe_to_deploy — CI/CD deploy safety check based on health scores, predictions, and active incidentsget_executive_summary — Infrastructure health summary for standups, weekly reports, or status updatesInstallation goes through your MCP client rather than a global install: point it at @uptimebolt/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: UPTIMEBOLT_API_KEY, UPTIMEBOLT_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Uptimebolt's toolset — get_service_status, get_monitors, get_monitor_health and 7 more — is a fair guide to whether it matches your workflow. It is maintained by clm-cloud-solutions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_service_status | Health status of business services with health score (0-100), monitor breakdown, and active incidents |
| get_monitors | List all monitors with operational status, response time, and uptime percentage |
| get_monitor_health | Detailed health for a specific monitor including response time trends and active predictions |
| get_monitor_metrics | Response time stats (avg, p95, p99), uptime percentage, and error breakdown |
| get_incidents | Active and resolved incidents with optional AI root cause analysis details |
| get_predictions | AI predictions for upcoming issues with confidence levels and predicted impact |
| get_deployments | Recent deployments with automatic incident correlation (GitHub/GitLab) |
| run_root_cause_analysis | AI-powered RCA using multi-model analysis (Claude, GPT) with deploy correlation |
| is_safe_to_deploy | CI/CD deploy safety check based on health scores, predictions, and active incidents |
| get_executive_summary | Infrastructure health summary for standups, weekly reports, or status updates |
Or without global install, using npx:
```json
{
"mcpServers": {
"uptimebolt": {
"command": "npx",
"args": ["-y", "--package=@uptimebolt/mcp-server", "uptimebolt-mcp"],
"env": {
"UPTIMEBOLT_API_KEY": "your-api-key",
"UPTIMEBOLT_API_URL": "https://api.uptimebolt.io"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UPTIMEBOLT_API_KEY | Credential the server authenticates with. | Yes |
| UPTIMEBOLT_API_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.