
Rootly
io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v1.2.9更新於 Oct 24, 2026
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
發布方自己的服務:Rootly
概覽
面向 Rootly 事件管理的本機 MCP 伺服器,讓助理列出、建立、更新與解決事件和警示,並讀取值班表與組織資訊。
- 可以做什麼
- 透過導覽工具在事件、警示、值班表、組織等領域間切換,查看連線狀態或返回選單。列出、查看、建立、更新與解決事件,可依狀態與嚴重程度篩選。列出、建立、更新、確認與解決警示。列出並查看值班表。列出團隊與嚴重程度,取得目前通過驗證的使用者。在支援 MCP Apps 的宿主中,事件查詢會顯示為唯讀卡片,呈現狀態、嚴重程度、服務、環境、團隊與生命週期時間軸。
- 適用情境
- 適合讓助理參與 Rootly 事件應變:分流或彙整事件、確認或解決警示、建立或更新事件,以及查詢誰在值班、有哪些團隊與嚴重程度。
- 執行需求
- 以本機程序執行(可用 Node.js 從原始碼建置,或使用已發布的容器映像走 stdio)。stdio 與 env 驗證模式需要 ROOTLY_API_TOKEN 中的 Rootly API 權杖,可於 Rootly 個人資料取得。HTTP 模式另需 CONDUIT_S2S_SECRET;gateway 模式要求每個請求在 X-Rootly-Api-Token 標頭中攜帶 Rootly 權杖。需要連線至 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版本歷史
4- v1.2.9最新Oct 14, 2026
- v1.2.8Oct 13, 2026
- v1.2.7Oct 9, 2026
- v1.2.6Sep 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-technology 發布
讓助理透過決策樹式工具集讀取與管理 Rootly 的事件、告警、值班排程與組織資料。

Rootly MCP
由 GitHub 帳號 Servosity 發布
非官方本機 MCP 伺服器,讓助理以具型別的 Rootly 事件、告警與值班指令操作,並附本機 SQLite 鏡像供離線分析。

Rootly
com.mcparmory
一個在本機執行的 MCP 伺服器,讓助理連接 Rootly,管理事件告警、事件記錄與含自訂自動化的工作流程。