Uptimebolt Mcp Server

io.github.clm-cloud-solutions由 GitHub 账号 clm-cloud-solutions 发布v1.0.7更新于 Oct 24, 2026

AI-powered infrastructure monitoring — health, incidents, predictions, RCA, deploy safety

概览

AI 生成的概览

UptimeBolt 的 MCP 服务器让 AI 助手查询基础设施监控数据:服务健康、事件、预测、根因分析与部署安全性。

可以做什么
  • 查询业务服务与监控项的健康状态、响应时间和可用率
  • 查看进行中与已解决的事件,并可附带 AI 根因分析
  • 获取即将发生问题的 AI 预测,含置信度与预计影响
  • 列出近期部署并自动关联 GitHub/GitLab 事件
  • 执行多模型根因分析并给出部署安全结论
  • 生成基础设施健康的高管摘要,用于站会或报告
适用场景
适合已使用 UptimeBolt 的 DevOps 与 SRE 团队:用自然语言询问基础设施状况、排查事件与部署关联,或在 CI/CD 流程中以部署安全检查作为门禁。
运行要求
通过 npm 包以 stdio 在本地运行(需 Node.js),也可作为 HTTP/Docker 服务运行。需要 UptimeBolt 账号与 API 密钥:stdio 模式使用 UPTIMEBOLT_API_KEY,HTTP 模式使用 x-api-key 请求头。UPTIMEBOLT_API_URL 用于设置 API 地址。需能访问 UptimeBolt API。
安装前请注意
需要 UptimeBolt API 密钥,该密钥可访问你的监控数据,请勿写入共享配置或日志。监控数据(含部署与事件详情)会发送至 UptimeBolt API 及其 AI 分析模型。该服务器以读取为主,但部署安全结果可能被用于拦截真实部署。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Uptimebolt Mcp Server,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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)

bash
npm install -g @uptimebolt/mcp-server

Claude Desktop (stdio)

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

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:

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"      }    }  }}

Claude Code / Cursor

Add to your project's .mcp.json:

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

Docker (HTTP)

bash
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:

json
{  "mcpServers": {    "uptimebolt": {      "command": "npx",      "args": ["-y", "mcp-remote", "http://localhost:3100/mcp", "--header", "x-api-key:your-api-key"]    }  }}

npm (programmatic)

bash
npm install @uptimebolt/mcp-server
typescript
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:

bash
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

bash
git clone https://github.com/clm-cloud-solutions/uptimebolt-mcp-server.gitcd uptimebolt-mcp-servercp .env.example .env          # configure your environmentnpm installnpm run dev          # stdio modenpm run dev:http     # HTTP modenpm run build        # compile TypeScriptnpm 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

来源:README.md,提交 736a07b

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.0.7最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分