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 分