
Rootly
io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.2.9Updated Oct 24, 2026
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
The publisher's own server: Rootly
Overview
Local MCP server for Rootly incident management, letting an assistant list, create, update and resolve incidents and alerts, and read on-call schedules and org.
- What you can do
- Navigate between domains (incidents, alerts, schedules, org) and check connection status or return to the menu with navigation tools. List, get, create, update and resolve incidents, with optional status and severity filters. List, create, update, acknowledge and resolve alerts. List and read on-call schedules. List teams and severity levels and fetch the current authenticated user. In MCP Apps hosts, an incident lookup renders as a read-only card with status, severity, services, environments, teams and a lifecycle timeline.
- When to use it
- Useful when an assistant should work with Rootly incident response: triaging or summarizing incidents, acknowledging or resolving alerts, creating or updating incidents, or checking who is on call and which teams and severities exist.
- Requirements
- Runs as a local process (Node.js build from source, or the published container image over stdio). Needs a Rootly API token in ROOTLY_API_TOKEN for stdio and env auth mode, obtained from Rootly profile settings. HTTP mode additionally requires CONDUIT_S2S_SECRET; gateway mode expects the Rootly token per request in the X-Rootly-Api-Token header. Network access to the Rootly API.
Installation
In SourceWeft
- Open Rootly in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Source: README.md at commit 514e44d
Tools
0Version history
4- v1.2.9LatestOct 14, 2026
- v1.2.8Oct 13, 2026
- v1.2.7Oct 9, 2026
- v1.2.6Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Rootly integrations

Rootly
com.rootlyOfficial publisher
Rootly MCP server for incident management, on-call scheduling and incident analysis, usable as a hosted endpoint or a local Python process.

On-Call Health
Published by GitHub account Rootly-AI-Labs
Connects an assistant to On-Call Health so it can run burnout-risk analyses and surface at-risk or healthy on-call responders.

Rootly
Published by GitHub account wyre-technology
Lets an assistant read and manage Rootly incidents, alerts, on-call schedules, and organization data through a decision-tree tool set.

Rootly MCP
Published by GitHub account Servosity
Unofficial local MCP server that gives an assistant typed Rootly incident, alert and on-call commands backed by a local SQLite mirror for offline analytics.

Rootly
com.mcparmory
A locally run MCP server that connects an assistant to Rootly for managing incident alerts, events and workflows with custom automations.