跳过安装。2 分钟内即可运行。
在 cloud.anythingmcp.com 开始免费试用，一键添加 Better Stack，然后将你的 AI 客户端（Claude、ChatGPT、Copilot 或 Cursor）指向生成的 MCP 端点。无需 Docker，无需 git clone，无需任何工程经验。
摘要
Better Stack 可用性监控与事件管理：带可用率和响应时间的监控器与心跳，可确认、升级和解决的事件，值班日历，升级策略，状态页和状态报告，以及已配置的集成。
试试这样问
Better Stack 的示例提示
点击任意提示即可复制，然后粘贴到 Claude、ChatGPT、Cursor、Gemini、Copilot 或 OpenClaw 中，在该连接器上运行。
Better Stack · 通过 MCP 实时
分享Claude 是 AI，可能会出错。请核对回答。
💡 无需安装? 直接使用 cloud.anythingmcp.com。 登录、点击 Connectors → Better Stack、粘贴凭证、生成 MCP API key，即可完成。无 Docker、无
git clone、无本地服务器。
Better Stack
Better Stack 可用性监控与事件管理：带可用率和响应时间的监控器与心跳，可确认、升级和解决的事件，值班日历，升级策略，状态页和状态报告，以及已配置的集成。
设置
设置大约需要 2 分钟。连接器使用 Better Stack Incidents API（前身为 Better Uptime，https://incidents.betterstack.com/api）。
- 打开 https://betterstack.com/settings/api-tokens/0，选择你的团队，在 Incidents API tokens 下复制或创建一个令牌。这种团队级令牌最简单。
- 全局 API 令牌（https://betterstack.com/settings/global-api-tokens）也可以使用，能访问所有团队。使用它时，AI 会传入
team_name来筛选列表，创建监控器、心跳或事件时也必须提供。 - 把令牌粘贴到
BETTER_STACK_API_TOKEN。写入操作需要具有写权限的令牌。 - 安装连接器并运行
better_stack_list_monitors检查令牌。
可读取的内容：
- 可用性监控器：状态（
up、down、paused、validating、maintenance）、URL、类型、检查频率、区域和最近一次检查；单个监控器的完整配置、某段日期的可用率（SLA），以及最近 24 小时各区域的响应时间。监控器分组及分组内的监控器。 - 用于定时任务和后台任务的心跳：ping URL、周期、宽限时间和状态，它们的可用率，以及心跳分组。
- 事件（从新到旧）：原因、状态、开始、确认和解决时间以及处理人，可按日期、监控器、心跳、是否已解决或已确认筛选；单个事件及失败的响应；由告警、确认、升级、评论和状态页更新组成的时间线；以及它的评论。
- 谁在值班：带当前值班人员的值班日历、某个时间点的日历（团队默认日历用
default），以及某个时间窗口内的班次。带步骤的升级策略，以及带告警渠道的严重级别。 - 状态页、页面上展示的资源及其可用率和每日历史、状态报告及其更新。
- 配置：入站和出站 Webhook、Slack 集成，以及服务负责人或环境等元数据。
可写入的内容：监控器（better_stack_create_monitor、better_stack_update_monitor，计划维护前后用 better_stack_pause_monitor 和 better_stack_resume_monitor）；心跳（better_stack_create_heartbeat 返回任务每次运行后必须请求的 ping URL，better_stack_update_heartbeat）；事件（better_stack_create_incident、better_stack_acknowledge_incident、better_stack_escalate_incident、better_stack_resolve_incident、better_stack_reopen_incident、better_stack_add_incident_comment）；状态页（better_stack_create_status_report，情况变化时用 better_stack_add_status_update，修改标题或调整维护时间用 better_stack_update_status_report）。
所有工具在安装时都已开启，包括写入类工具。创建事件、升级事件和发布状态报告都会通知真实的人员或公开订阅者，所以 AI 会先向你确认；notify_subscribers: false 可以静默发布状态报告。如果解决的是一个仍在失败的监控器的事件，下一次检查会打开一个新事件。状态报告通过一条把所有受影响资源设为 resolved 的更新来关闭。
数据格式：响应遵循 JSON:API：data（单个对象或列表）包含 id、type、attributes 和 relationships；关联的用户和状态更新在 included 中。ID 是数字字符串。时间为 UTC 的 ISO 8601；日期筛选（from、to）使用 YYYY-MM-DD。可用率是百分比（99.98）；停机时间、事件时长和响应时间以秒为单位。事件的 status 为 Started、Acknowledged 或 Resolved。监控器密码、Playwright 环境变量和策略的事件令牌会从响应中去除。
翻页：列表返回 pagination.next，这是一个 URL，最后一页为 null；AI 会把该 URL 中的页码作为 page 再次调用。per_page 默认 50，最多 250；事件默认 10，最多 50。
常见错误：401 表示令牌错误或已撤销，或者用的是 Telemetry 令牌而不是 Incidents 令牌。403 是令牌没有写权限，404 是 ID 不存在或属于其他团队，422 是校验错误，errors 会指出字段，429 是速率限制。
该连接器不涵盖 Better Stack Telemetry（日志、指标、仪表盘），也不会删除监控器、心跳、事件或状态页。
前提条件: BETTER_STACK_API_TOKEN
本地安装连接器
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
打开 http://localhost:3000/connectors/store，选择 Better Stack 并填入前提条件中列出的环境变量。
可用工具
| Tool | What it does |
|---|---|
better_stack_list_monitors | List the team's uptime monitors with their status (up, down, paused, validating, maintenance), URL, type, check frequency, regions and last… |
better_stack_get_monitor | Get one monitor with its full configuration: type, URL, status, check frequency, regions, alert channels, escalation policy, maintenance… |
better_stack_create_monitor | Create an uptime monitor: an HTTP check (status, expected status code, keyword present or absent), a server or port check (ping, TCP, UDP… |
better_stack_update_monitor | Change a monitor: only the fields you pass are updated (URL, name, frequency, regions, alert channels, escalation policy, group… |
better_stack_pause_monitor | Pause a monitor: Better Stack stops checking it and sends no alerts until it is resumed |
better_stack_resume_monitor | Resume a paused monitor: checks and alerts start again with the monitor's existing settings |
better_stack_get_monitor_availability | Availability summary (SLA) of a monitor for a date range: availability percentage, total downtime in seconds, number of incidents, longest… |
better_stack_get_monitor_response_times | Response times of a monitor's checks over the last 24 hours, per region, oldest first: the total response time in seconds for each check |
better_stack_list_monitor_groups | List the monitor groups (the folders monitors are sorted into on the dashboard), with their name, paused flag and team |
better_stack_get_monitor_group | Get one monitor group by id: its name, sort index, paused flag, team and timestamps |
better_stack_list_monitor_group_monitors | List the monitors inside one monitor group, with the same fields as better_stack_list_monitors; paged with page and per_page |
better_stack_list_heartbeats | List heartbeat (cron job) monitors: name, status, expected period and grace in seconds, the ping URL the job must call, paused flag and… |
better_stack_get_heartbeat | Get one heartbeat monitor with its ping URL, period, grace, status, alert channels, escalation policy and maintenance window |
better_stack_create_heartbeat | Create a heartbeat monitor for a cron job or background task |
better_stack_update_heartbeat | Change a heartbeat monitor: name, period, grace, alert channels, group, escalation policy, or pause and resume it with paused |
better_stack_get_heartbeat_availability | Availability summary of a heartbeat for a date range: availability percentage, total downtime in seconds, number of incidents, longest and… |
better_stack_list_heartbeat_groups | List the heartbeat groups, with their name, paused flag, sort index and team |
better_stack_list_incidents | List incidents, newest first: name, cause, status (Started, Acknowledged, Resolved), start, acknowledge and resolve times and who did it… |
better_stack_get_incident | Get one incident with its cause, status, timestamps, who acknowledged and resolved it, alert channels, escalation policy, metadata and the… |
better_stack_get_incident_timeline | Timeline of an incident, newest first: alerts sent, acknowledgements, escalations, comments, status page updates and the captured responses |
better_stack_create_incident | Open a manual incident and alert the on-call person through the chosen channels (call, SMS, e-mail, push), optionally escalating with a… |
better_stack_acknowledge_incident | Acknowledge an ongoing incident: further escalation stops while the incident stays open until it is resolved |
better_stack_resolve_incident | Resolve an ongoing incident |
better_stack_reopen_incident | Reopen a resolved incident, for example when the problem came back right after it was marked as resolved |
better_stack_escalate_incident | Escalate an ongoing incident to a team member, a team, an on-call calendar, an escalation policy or the whole organization, choosing the… |
better_stack_list_incident_comments | List the comments posted on an incident, with their text (Markdown), author and timestamps |
better_stack_add_incident_comment | Post a comment on an incident, for example a status note or the root cause; it appears in the incident timeline |
better_stack_list_on_call_calendars | List on-call calendars (schedules) with their name, team and whether each is the team's default, plus who is on call right now |
better_stack_get_on_call_calendar | Who is on call on a calendar, now or at a given date and time: names, e-mails, phone numbers and holiday status of the on-call users |
better_stack_list_on_call_events | List the shifts of an on-call calendar in a time window: who is on call (e-mails), start and end time, and whether the shift is an override |
better_stack_list_escalation_policies | List escalation policies with their steps (who is alerted, after how many minutes, with which severity), repeat settings and fallback policy |
better_stack_get_escalation_policy | Get one escalation policy with its ordered steps, step members (users, on-call, Slack, webhooks), wait times, repeat count and fallback… |
better_stack_list_severities | List the severities (urgencies) of the team, with the alert channels each one uses (call, SMS, e-mail, push, critical alert) |
better_stack_list_status_pages | List the status pages: company name, subdomain and custom domain, published flag, overall state (operational, degraded, downtime… |
better_stack_get_status_page | Get one status page with its domain, overall state, published and subscribable flags, history length, design and access settings |
better_stack_list_status_page_resources | List the resources shown on a status page (monitors, heartbeats, groups) with their public name, current status, availability and daily… |
better_stack_list_status_reports | List the status reports (incident announcements and maintenance windows) on a status page with title, type, start and end, affected… |
better_stack_get_status_report | Get one status report on a status page with its type, start and end, affected resources, overall state and its status updates (in… |
better_stack_create_status_report | Publish a status report on a public status page: an incident announcement or a planned maintenance, with the affected resources and a first… |
better_stack_update_status_report | Change a status report's title or its start and end time, for example to reschedule a maintenance |
better_stack_list_status_updates | List the status updates posted on a status report, with message, publish time, affected resources and whether subscribers were notified |
better_stack_add_status_update | Post a new update on a status report, e.g. investigating, identified, monitoring or resolved; set every affected resource to resolved to… |
better_stack_list_incoming_webhooks | List the incoming webhook integrations that open and resolve incidents from other tools, with their name, URL and the rules for starting… |
better_stack_list_outgoing_webhooks | List the outgoing webhook integrations that Better Stack calls on incident and monitor events, with their name, target URL and triggers |
better_stack_list_slack_integrations | List the Slack integrations of the team: workspace, channel and the kinds of notifications sent there |
better_stack_list_metadata | List metadata records (key and values) attached to monitors, heartbeats, incidents and integrations, e.g. service owner or environment… |
示例提示
- “现在有什么宕机了吗？列出处于 down 状态的监控器及其 URL 和最近一次检查。”
- “https://shop.example.com 的监控器上个月可用率是多少？最长的一次事件是哪次？”
- “这周六 22:00 默认日历上谁在值班？”
- “显示未解决的事件及其原因和时间线，然后确认支付 API 的那个事件。”
- “在我们的状态页上发布一个周日 02:00 到 03:00 UTC 影响 API 的计划维护，不通知订阅者。先给我看文案。”
下一步
这份指南对你有帮助吗?