跳过安装。2 分钟内即可运行。
在 cloud.anythingmcp.com 开始免费试用，一键添加 Rootly，然后将你的 AI 客户端（Claude、ChatGPT、Copilot 或 Cursor）指向生成的 MCP 端点。无需 Docker，无需 git clone，无需任何工程经验。
摘要
在任意 AI 智能体中使用 Rootly 事件管理：宣布、更新、缓解和解决事件，附带时间线备注和行动项；确认和解决告警，查看谁在值班，在状态页发布更新，并读取复盘、服务、团队和严重级别。
试试这样问
Rootly 的示例提示
点击任意提示即可复制，然后粘贴到 Claude、ChatGPT、Cursor、Gemini、Copilot 或 OpenClaw 中，在该连接器上运行。
Claude 是 AI，可能会出错。请核对回答。
💡 无需安装? 直接使用 cloud.anythingmcp.com。 登录、点击 Connectors → Rootly、粘贴凭证、生成 MCP API key，即可完成。无 Docker、无
git clone、无本地服务器。
Rootly
在任意 AI 智能体中使用 Rootly 事件管理：宣布、更新、缓解和解决事件，附带时间线备注和行动项；确认和解决告警，查看谁在值班，在状态页发布更新，并读取复盘、服务、团队和严重级别。
设置
设置大约需要 2 分钟。你需要一个 Rootly 账户。
- 在 Rootly 中打开组织菜单，再打开 Organization Settings、API Keys，创建一个密钥。Global 密钥能看到整个组织，Team 密钥只能看到该团队的记录，Personal 密钥以你自己的权限操作。
- 给密钥分配一个能读取所需内容的角色；如果要让 AI 修改事件、告警和行动项，还要给它相应的写入权限。
- 只把密钥本身（前面不要加
Bearer）粘贴到ROOTLY_API_KEY，然后运行rootly_get_current_user。它会显示密钥以哪个用户身份操作；Global 和 Team 密钥会返回创建它的用户。
当前发生了什么：rootly_list_incidents 配合 status: "started,mitigated"（或 in_triage）列出进行中的事件，可按严重级别、服务、团队、环境、类型、文本和日期筛选。rootly_get_incident 显示单个事件的全部属性，rootly_list_incident_events 显示其时间线，rootly_list_incident_action_items 显示其任务。查找 id 时，AI 使用 rootly_list_severities、rootly_list_services、rootly_get_service、rootly_list_functionalities、rootly_get_functionality、rootly_list_teams、rootly_get_team、rootly_list_environments、rootly_list_incident_types 和 rootly_list_users。
处理事件：rootly_create_incident 用于宣布事件。带上 idempotency_key 后，24 小时内重试会返回同一个事件，而不是再开一个；kind 设为 test 可用于试运行。rootly_update_incident 修改标题、摘要、严重级别、服务、团队、标签或状态；传入的列表会替换整个列表。rootly_add_incident_event 向时间线添加内部或外部备注，rootly_mitigate_incident 和 rootly_resolve_incident 附一条简短说明推进事件。行动项：跨所有事件的 rootly_list_action_items、rootly_get_action_item、rootly_create_action_item 和 rootly_update_action_item（例如把状态改为 done）。
告警：rootly_list_alerts（例如状态 triggered 或 open），rootly_get_alert 含来源发送的原始负载，rootly_acknowledge_alert（升级策略不再呼叫下一级）以及 rootly_resolve_alert，后者还可以同时解决关联的事件。
值班：rootly_list_oncalls 回答现在或某个时间段内谁在值班。rootly_list_schedules、rootly_get_schedule、rootly_get_schedule_shifts、rootly_list_shifts 和 rootly_list_escalation_policies 提供详细信息。
状态页和复盘：rootly_list_status_pages、rootly_get_status_page 和 rootly_list_incident_status_page_events 用于读取；rootly_create_status_page_event 发布更新（investigating、identified、monitoring、resolved）。rootly_list_retrospectives 和 rootly_get_retrospective 读取事后复盘。
写入之前：普通事件会运行工作流、创建 Slack 频道并可能呼叫相关人员；状态页更新是公开的，还可能给订阅者发邮件。因此 AI 会先展示将要执行的操作，等你确认。私有事件无法再改回公开。
安装时关闭：没有。所有工具一开始就是开启的；AI 能做什么由密钥的角色和团队决定。
数据格式：响应遵循 JSON:API：记录在 data 中（id、type、attributes、relationships），通过 include 嵌入的记录在 included 中。id 是 UUID，用户 id 是数字。便于阅读的事件编号是 attributes.sequential_id（INC-123）。时间为 ISO 8601，未指定时区时为 UTC。rootly_list_incidents 和 rootly_list_alerts 默认只返回一组精简属性；fields: "" 返回全部属性。事件响应中不包含 Zoom 会议密码和主持人链接。
分页：列表返回 meta，含 current_page、next_page（最后一页为 null）、total_count 和 total_pages；AI 带上 page_number 再次调用。事件和告警还支持来自 meta.next_cursor 的游标 page_after。page_size 最大 100，但 Rootly 记录很大，小分页效果更好。
常见错误：401 表示密钥错误或已撤销，403 表示密钥的角色或团队不允许该调用，404 表示 id 未知或不在密钥所属团队内，422 表示校验错误，errors 会指出字段，429 表示触发速率限制（X-RateLimit-* 响应头说明何时重置；稍等后重试）。
该连接器不会删除事件、告警或行动项，不会修改排班、升级策略或状态页，也不会撰写复盘。
前提条件: ROOTLY_API_KEY
本地安装连接器
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，选择 Rootly 并填入前提条件中列出的环境变量。
可用工具
| Tool | What it does |
|---|---|
rootly_get_current_user | Show the user the API key acts as: id, name, email, time zone and role |
rootly_list_incidents | List incidents, newest first by default: sequential id (the 123 in INC-123), title, status, kind, severity, services, teams, environments… |
rootly_get_incident | Get one incident with all its attributes: title, summary, status, severity, services, teams, environments, types, labels, Slack channel… |
rootly_create_incident | Declare an incident |
rootly_update_incident | Change an incident: title, summary, status, severity, affected services, functionalities, environments, types, teams, causes or labels |
rootly_mitigate_incident | Mark an incident as mitigated (the impact is under control) with a short note on how |
rootly_resolve_incident | Mark an incident as resolved with a short note on how |
rootly_list_incident_events | List the timeline of an incident: the events (notes, status changes, updates) with their text, visibility (internal or external) and when… |
rootly_add_incident_event | Add a note to the timeline of an incident |
rootly_list_action_items | List action items across all incidents: summary, kind (task during the incident, follow_up after it), priority, status, assignee, due date… |
rootly_list_incident_action_items | List the action items of one incident: summary, kind, priority, status, assignee and due date |
rootly_get_action_item | Get one action item with its description, assignee, teams, due date and linked Jira issue |
rootly_create_action_item | Add an action item to an incident: a task to do now or a follow-up for after the incident, with priority, assignee and due date |
rootly_update_action_item | Change an action item: summary, description, status (e.g. done), priority, assignee or due date |
rootly_list_alerts | List alerts, newest first: short id, summary, status (open, triggered, acknowledged, resolved, deferred), source (datadog, grafana, email… |
rootly_get_alert | Get one alert with its full details, including the raw payload the source sent (data), labels, responders and linked incidents |
rootly_acknowledge_alert | Acknowledge an alert: someone is looking at it, so its escalation stops paging the next level |
rootly_resolve_alert | Resolve an alert, optionally with a note and also resolving the incidents it is attached to |
rootly_list_services | List the services in the catalog: name, slug, description, owners, linked repositories and external ids (Backstage, Cortex, OpsLevel… |
rootly_get_service | Get one service with its description, owner teams and users, escalation policy, alert and incident broadcast settings and external links |
rootly_list_functionalities | List the functionalities (user-facing capabilities such as Checkout or Login) with name, slug, description and owners |
rootly_get_functionality | Get one functionality with its description, owners, linked services and status page components |
rootly_list_teams | List the teams (groups) with name, slug, description, members and their on-call and escalation settings |
rootly_get_team | Get one team with its description and members; add include for its schedules and escalation policies |
rootly_list_environments | List the environments (production, staging and so on) with name, slug and colour |
rootly_list_severities | List the severity levels (e.g |
rootly_list_incident_types | List the incident types (e.g |
rootly_list_users | List the users of the organization: id, name, email, time zone; add include for role, teams or schedules |
rootly_list_oncalls | Who is on call: the on-call entries of every escalation policy, schedule and level for now or a time window, with the user, schedule… |
rootly_list_schedules | List the on-call schedules with name, description, owning teams and time zone |
rootly_get_schedule | Get one on-call schedule with its owners, time zone and settings |
rootly_get_schedule_shifts | List the shifts of one schedule in a time window: who is on call from when to when, including overrides |
rootly_list_shifts | List on-call shifts across schedules in a time window (default: the shifts running now): schedule, rotation, user, start and end, override… |
rootly_list_escalation_policies | List the escalation policies with name, description, repeat settings and owning teams; add include for their levels and paths |
rootly_list_status_pages | List the status pages with title, public URL, whether they are public, and their settings |
rootly_get_status_page | Get one status page with its title, description, public URL, components and settings |
rootly_list_incident_status_page_events | List the updates an incident published to status pages: text, status (investigating, identified, monitoring, resolved), status page and time |
rootly_create_status_page_event | Publish an incident update on a status page, e.g |
rootly_list_retrospectives | List incident retrospectives (post-mortems): title, status (draft, published), the incident, URL and dates |
rootly_get_retrospective | Get one retrospective with its title, status, content, URL and the incident it belongs to |
示例提示
- “现在有哪些事件还在进行中？支付服务谁在值班？”
- “给我看 INC-482 的时间线，并列出它未完成的行动项。”
- “为 checkout 服务结账缓慢的问题宣布一个 SEV2 事件。创建前先给我看详细内容。”
- “确认 API 网关上已触发的 Datadog 告警，并告诉我它们的内容。”
- “在我们的状态页上为 INC-482 发布一条 Monitoring 更新：修复已上线，我们正在观察错误率。”
下一步
这份指南对你有帮助吗?