Better Stack MCP by usefulapi

io.usefulapi由 usefulapi.io 發布官方發布者v1.37.4更新於 Nov 7, 2026

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

發布方自己的服務：Ably MCP by usefulapi

已驗證Streamable HTTP可網頁執行雲端與基礎設施安全與監控

服務詳細資訊

識別碼: io.usefulapi/betterstack
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 usefulapi.io，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Fbetterstack.svg)](https://sourceweft.com/mcp/io.usefulapi%2Fbetterstack?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

針對 Better Stack Uptime 的託管 MCP 伺服器：讓助理讀取監控項目、事件、心跳、值班表和狀態頁，並可確認或解決事件。

可以做什麼: 列出並檢視監控項目的狀態、檢查頻率、區域和告警設定
列出並檢視事件的原因、時間軸時間戳以及確認或解決的人員
列出排程／背景工作的心跳及其週期、寬限時間和狀態
列出值班表與目前值班人員，以及狀態頁及其彙總狀態
確認或解決進行中的事件
查看本月工具呼叫用量、提出功能需求或管理 Pro 訂閱
適用情境: 適合想透過對話了解目前故障、近期事件紀錄或誰在值班，並直接在聊天中確認或解決事件，而不必開啟 Better Stack 主控台的場合。
執行需求: 透過 streamable HTTP 連線的遠端端點，無需本機安裝。以 OAuth 登入，首次連線時需貼上 Better Stack API 權杖（Better Stack → Settings → API tokens），依使用者儲存。用戶端設定中不要填入 API 金鑰或 Authorization 標頭。超出免費每月呼叫額度後需要付費方案。

安裝前請注意

OAuth 登入過程中會要求提供 Better Stack API 權杖，並由第三方託管方儲存。確認與解決工具會改變事件狀態並停止或關閉升級通知，執行前應先確認。用量按呼叫計費：免費方案每月 50 次工具呼叫；升級工具會回傳 Pro（每月 9 美元）或 Pro+（每月 39 美元）的 Stripe 結帳連結；取消後服務持續到已付費週期結束，當期不退款。

安裝

在 SourceWeft 中

開啟儀表板中的 Better Stack MCP by usefulapi，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.usefulapi%2Fbetterstack/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "better-stack-by-usefulapi": {
      "type": "http",
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

README

Better Stack MCP by usefulapi

Manage Better Stack Uptime from Claude, Cursor, or any MCP client — read monitors, incidents, heartbeats, on-call schedules and status pages, and acknowledge/resolve incidents. Hosted, no local install: connect with your Better Stack API token.

Live endpoint: https://betterstack.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://betterstack.usefulapi.io/mcp.
Claude Code: claude mcp add --transport http betterstack https://betterstack.usefulapi.io/mcp, then run /mcp to log in.
VS Code: Add to VS Code.
Cursor and other clients: add the URL as a remote MCP server:

json

{  "mcpServers": {    "betterstack": {      "url": "https://betterstack.usefulapi.io/mcp"    }  }}

{  "mcpServers": {    "betterstack": {      "url": "https://betterstack.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Better Stack credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/betterstack/

On first connect you'll paste your Better Stack API token (Better Stack → Settings → API tokens). It's validated, stored per-user, and scoped to you — no keys in config files.

Tools

Tool	Type	What it does
`betterstack_list_monitors`	read	List monitors
`betterstack_get_monitor`	read	Get a monitor
`betterstack_list_incidents`	read	List incidents
`betterstack_get_incident`	read	Get an incident
`betterstack_list_heartbeats`	read	List heartbeats
`betterstack_list_on_call`	read	List on-call schedules
`betterstack_list_status_pages`	read	List status pages
`betterstack_acknowledge_incident`	write	Acknowledge an incident
`betterstack_resolve_incident`	write	Resolve an incident
`betterstack_usage_status`	meta	Usage status (free-tier meter)
`betterstack_request_feature`	meta	Request a missing feature
`betterstack_upgrade`	meta	Upgrade to Pro or Pro+
`betterstack_cancel_subscription`	meta	Cancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with betterstack_upgrade (it returns a Stripe Checkout link). Cancel any time with betterstack_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running betterstack_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

來源：servers/betterstack/README.md，提交 4046075

工具

betterstack_list_monitors

List monitors

List 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.

輸入參數urlpageper_pageteam_namepronounceable_name

betterstack_get_monitor

Get a monitor

Get 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}.

輸入參數monitor_id必填

betterstack_list_incidents

List incidents

List 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.

輸入參數tofrompageper_pageresolvedteam_namemonitor_idacknowledgedheartbeat_id

betterstack_get_incident

Get an incident

Get 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}.

輸入參數incident_id必填

betterstack_list_heartbeats

List heartbeats

List 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.

輸入參數pageper_pageteam_name

betterstack_list_on_call

List on-call schedules

List 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.

輸入參數pageper_pageteam_name

betterstack_list_status_pages

List status pages

List public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.

輸入參數pageper_pageteam_name

betterstack_acknowledge_incident

Acknowledge an incident

Acknowledge 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.

輸入參數incident_id必填acknowledged_by必填

betterstack_resolve_incident

Resolve an incident

Resolve 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.

輸入參數incident_id必填resolved_by必填