mcpField
U
uptimebolt-mcp-server

uptimebolt-mcp-server

Local
github.com/clm-cloud-solutionsCloud & Infra2Updated 34w ago

About uptimebolt-mcp-server

uptimebolt-mcp-server connects MCP clients to UptimeBolt monitoring data for DevOps and SRE teams. Its tools cover service health, predictions, incident analysis, deployment correlation, and deployment safety checks.

Key features

  1. 01Service and monitor health
  2. 02Incident and prediction queries
  3. 03AI root cause analysis
  4. 04Deployment and incident correlation
  5. 05CI/CD deployment safety checks
  6. 06Local stdio and remote HTTP

Use cases

  1. 01Check infrastructure health from an MCP client
  2. 02Investigate causes of service incidents
  3. 03Review whether a deployment is safe
  4. 04Add health checks to a CI/CD pipeline

MCP support

Exposes 10 UptimeBolt monitoring tools to MCP clients over stdio or HTTP. Access uses an API key, provided as an environment variable in stdio mode or a request header in HTTP mode.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"clm-cloud-solutions-uptimebolt": {
"command": "npx",
"args": [
"-y",
"@uptimebolt/mcp-server"
]
}
}
}
Run commandnpx -y @uptimebolt/mcp-server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@uptimebolt/mcp-server1.0.7

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

UptimeBolt MCP Server

AI-powered infrastructure monitoring tools for Claude, Claude Code, Cursor, and any MCP-compatible client.

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.

Built by CLM Cloud Solutions in Madrid, Spain.

Why UptimeBolt MCP Server?

Ask your infrastructure questions in natural language. Instead of navigating dashboards, let your AI assistant query real-time monitoring data directly:

  • "Is it safe to deploy right now?" — get a data-driven answer based on health scores, active incidents, and predictions
  • "What caused the last incident?" — AI-powered root cause analysis with deploy correlation
  • "Give me an executive summary of the last 24 hours" — ready for your standup or status report
  • "Show me monitors that are degraded" — instant filtered view across your infrastructure

Features

  • 10 monitoring tools — service status, incidents, predictions, RCA, deploy safety, and more
  • Dual transport — stdio (local) + HTTP (remote/CI-CD)
  • API key authentication — secure per-request access to your UptimeBolt data
  • Works everywhere — Claude Desktop, Claude Code, Cursor, Cline, and any MCP client
  • CI/CD ready — deploy safety checks directly in your pipeline

Quick Start

Install globally (recommended)
npm install -g @uptimebolt/mcp-server
Claude Desktop (stdio)

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "uptimebolt": {
      "command": "uptimebolt-mcp",
      "env": {
        "UPTIMEBOLT_API_KEY": "your-api-key",
        "UPTIMEBOLT_API_URL": "https://api.uptimebolt.io"
      }
    }
  }
}

Or without global install, using npx:

{
  "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"
      }
    }
  }
}
Claude Code / Cursor

Add to your project's .mcp.json:

{
  "mcpServers": {
    "uptimebolt": {
      "command": "uptimebolt-mcp",
      "env": {
        "UPTIMEBOLT_API_KEY": "your-api-key",
        "UPTIMEBOLT_API_URL": "https://api.uptimebolt.io"
      }
    }
  }
}
Docker (HTTP)
docker run -p 3100:3100 \
  -e UPTIMEBOLT_API_URL=https://api.uptimebolt.io \
  ghcr.io/clm-cloud-solutions/uptimebolt-mcp-server:latest

Then connect via mcp-remote:

{
  "mcpServers": {
    "uptimebolt": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://localhost:3100/mcp", "--header", "x-api-key:your-api-key"]
    }
  }
}
npm (programmatic)
npm install @uptimebolt/mcp-server
import { TOOLS, HANDLERS } from "@uptimebolt/mcp-server";

// TOOLS — MCP tool definitions (10 tools)
// HANDLERS — tool handler functions: (args, context?) => Promise<result>

Available Tools

ToolDescription
get_service_statusHealth status of business services with health score (0-100), monitor breakdown, and active incidents
get_monitorsList all monitors with operational status, response time, and uptime percentage
get_monitor_healthDetailed health for a specific monitor including response time trends and active predictions
get_monitor_metricsResponse time stats (avg, p95, p99), uptime percentage, and error breakdown
get_incidentsActive and resolved incidents with optional AI root cause analysis details
get_predictionsAI predictions for upcoming issues with confidence levels and predicted impact
get_deploymentsRecent deployments with automatic incident correlation (GitHub/GitLab)
run_root_cause_analysisAI-powered RCA using multi-model analysis (Claude, GPT) with deploy correlation
is_safe_to_deployCI/CD deploy safety check based on health scores, predictions, and active incidents
get_executive_summaryInfrastructure health summary for standups, weekly reports, or status updates

Authentication

Get your API key at app.uptimebolt.io/settings/api-keys.

  • stdio mode: Set UPTIMEBOLT_API_KEY environment variable
  • HTTP mode: Pass x-api-key header with each request (no startup key required)

CI/CD Integration

Use is_safe_to_deploy as a gate in your deployment pipeline:

curl -X POST http://localhost:3100/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "x-api-key: your-api-key" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "is_safe_to_deploy",
      "arguments": { "service_name": "my-service" }
    }
  }'

The response includes a risk level (low, medium, high), active issues, and a recommendation (proceed, proceed_with_caution, wait_and_monitor).

Configuration

VariableDescriptionDefault
UPTIMEBOLT_API_KEYYour UptimeBolt API key(required for stdio)
UPTIMEBOLT_API_URLUptimeBolt API base URLhttp://localhost:3200
MCP_HTTP_PORTHTTP server port3100
NODE_ENVEnvironment (production disables console logs)development
LOG_LEVELLog level (error, warn, info, debug)debug (dev) / info (prod)

Development

git clone https://github.com/clm-cloud-solutions/uptimebolt-mcp-server.git
cd uptimebolt-mcp-server
cp .env.example .env          # configure your environment
npm install
npm run dev          # stdio mode
npm run dev:http     # HTTP mode
npm run build        # compile TypeScript
npm run typecheck    # type check without emitting

About UptimeBolt

UptimeBolt is an AI-first SaaS monitoring platform for DevOps teams and SREs. Key capabilities:

  • Cascade failure prediction — dependency graph with what-if analysis, downtime cost estimation, and proactive mitigations
  • Deploy correlation + RCA 2.0 — automatically correlates GitHub/GitLab deploys with incidents, identifies the responsible commit and files
  • AI Copilot — conversational assistant with real-time infrastructure context
  • 8 monitor types — HTTP, TCP, DNS, Database, Email, Synthetic, Push, Ping

About CLM Cloud Solutions

CLM Cloud Solutions S.L. is a technology company based in Madrid, Spain, building SaaS products for engineering teams to operate with confidence, speed, and security.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.