
Rootly
io.github.wyre-technology由 GitHub 账号 wyre-technology 发布v1.2.4更新于 Oct 24, 2026
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
发布方自己的服务:Rootly
概览
让助手通过决策树式工具集读取和管理 Rootly 的事件、告警、值班排班与组织数据。
- 可以做什么
- 将助手连接到 Rootly 事件管理平台。工具按域组织,通过 rootly_navigate 进入:incidents(列出、获取、创建、更新、解决)、alerts(列出、确认、解决、创建、更新)、schedules(列出、获取)以及 org(团队、严重级别、当前用户)。rootly_status 检查连接状态,rootly_back 返回菜单。在支持 MCP Apps 的宿主中,rootly_incidents_get 会渲染为只读的事件卡片。
- 适用场景
- 适合让助手分诊或汇报事件与告警、查询值班排班,或在值班与事后复盘中创建和更新事件记录。适用于已经在使用 Rootly、希望从聊天客户端访问事件数据的团队。
- 运行要求
- 以本地进程方式运行(Node.js 构建,或已发布的容器镜像),通过 stdio 通信;设置 MCP_TRANSPORT 为 http 时也可使用 HTTP 流式传输。需要 Rootly API 令牌,通过 ROOTLY_API_TOKEN 提供,可从 Rootly 个人资料页获取。AUTH_MODE 决定令牌是从环境变量读取还是由网关以请求头注入。需要访问 Rootly API 的网络连接。
安装
在 SourceWeft 中
- 打开 控制台中的 Rootly,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
rootly-mcp
MCP server for the Rootly incident management platform.
Built by WYRE Technology — part of the wyre-projects MCP server collection.
Uses decision-tree navigation: start with rootly_navigate to select a domain, then use that domain's tools. Call rootly_back to return.
Domains & Tools
Navigation (always available)
Domain: incidents
Domain: alerts
Domain: schedules
Domain: org
Interactive Incident Card (MCP Apps)
rootly_incidents_get renders as an interactive read-only card in MCP Apps
hosts (Claude Desktop/web) showing status, severity, services, environments,
teams, and a lifecycle timeline; plain-JSON behavior is unchanged in other
hosts. The card is neutral by default and brandable via window.__BRAND__
injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL,
MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG,
MCP_BRAND_TEXT) — no rebuild needed. Rebuild the card bundle itself with
npm run build:ui (only needed when ui/ changes; the embedded output is
committed).
Setup
1. Install & build
2. Set your API token
Get your token from Rootly → Profile → API Tokens.
3. Run (stdio — for mcporter/Claude Desktop)
4. Run (HTTP streaming transport)
CONDUIT_S2S_SECRET is required. If it is empty or a known placeholder (changeme, change-me, secret, example, placeholder, replace-me, your-secret, your-s2s-secret, s2s-secret, replace-with-a-real-secret), the HTTP server logs an error and exits non-zero. It never prints the secret.
/health stays unauthenticated, does not require X-Gateway-S2S, and does not return the API token. The stdio transport does not use CONDUIT_S2S_SECRET.
5. Run with Docker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode the Rootly token arrives on each request as X-Rootly-Api-Token; it is not read from the environment.
Do not pass a known placeholder such as your-s2s-secret or changeme. Startup treats those as unset and exits. Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, does not pass ROOTLY_API_TOKEN, and publishes 127.0.0.1:8080:8080. A project .env is interpolation only — do not add env_file to the gateway service.
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses ROOTLY_API_TOKEN:
Configuration
Copy .env.example and set the variables below.
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The value is t=<unix seconds>,v1=<hex hmac-sha256>. The hex digest is HMAC-SHA256 over the exact ASCII string t=<unix seconds> (the same prefix that appears in the header), keyed with CONDUIT_S2S_SECRET, encoded as 64 lowercase hex characters. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401. The secret is never written to logs or the response.
In AUTH_MODE=gateway, /mcp also requires X-Rootly-Api-Token. That header is the only Rootly credential for the request. A request without it returns 401 and does not fall back to ROOTLY_API_TOKEN.
mcporter Configuration
Then: mcporter call rootly.rootly_navigate --domain alerts
Claude Desktop (MCPB)
Download the .mcpb bundle from Releases and install it in Claude Desktop.
Or manually add to claude_desktop_config.json:
Rate Limiting
Rootly enforces 3 write operations per 60 seconds. The server tracks this in-process and returns a descriptive error with retry-after time if exceeded.
API Reference
- Rootly API docs: https://docs.rootly.com/api-reference
- API base URL:
https://api.rootly.com/v1 - Auth:
Authorization: Bearer <token> - Write content-type:
application/vnd.api+json
Development
License
Apache-2.0 © WYRE Technology
来源:README.md,提交 514e44d
工具
0版本历史
1- v1.2.4最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。
其他 Rootly 集成

Rootly
com.rootly官方发布者
Rootly 的 MCP 服务器,用于事件管理、值班排班与事件分析,可作为托管端点或本地 Python 进程运行。

On-Call Health
由 GitHub 账号 Rootly-AI-Labs 发布
将助手连接到 On-Call Health,用于运行值班倦怠风险分析,并找出高风险或状态良好的值班人员。

Rootly
由 GitHub 账号 WYRE-AI 发布
面向 Rootly 事件管理的本地 MCP 服务器,让助手列出、创建、更新和解决事件与告警,并读取值班表和组织信息。

Rootly MCP
由 GitHub 账号 Servosity 发布
非官方本地 MCP 服务器,为助手提供类型化的 Rootly 事件、告警与值班命令,并配有本地 SQLite 镜像用于离线分析。

Rootly
com.mcparmory
一个本地运行的 MCP 服务器,让助手连接 Rootly,管理事件告警、事件记录和带自定义自动化的工作流。