rootly-mcp
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)
Tool | Description |
| Navigate to a domain: |
| Check connection status and available domains |
| Return to the navigation menu |
Domain: incidents
Tool | Description |
| List incidents with optional status/severity filters |
| Get a single incident by ID |
| Create a new incident |
| Update title, summary, status, or severity |
| Resolve an incident |
Domain: alerts
Tool | Description |
| List alerts with optional status filter |
| Acknowledge an alert |
| Resolve an alert |
| Create a new alert |
| Update alert status or summary |
Domain: schedules
Tool | Description |
| List on-call schedules |
| Get a single on-call schedule |
Domain: org
Tool | Description |
| List teams |
| List severity levels |
| Get current authenticated user |
Related MCP server: OpsLevel MCP
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
cd rootly-mcp
npm install
npm run build2. Set your API token
export ROOTLY_API_TOKEN=rootly_xxxxxxxxxxxxxxxxGet your token from Rootly → Profile → API Tokens.
3. Run (stdio — for mcporter/Claude Desktop)
ROOTLY_API_TOKEN=your_token node dist/index.js4. 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.
# Refuses to start until CONDUIT_S2S_SECRET is set. With a secret and no
# MCP_HTTP_HOST, the process binds 0.0.0.0 (same as container deploys).
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
ROOTLY_API_TOKEN=your_token \
MCP_HTTP_HOST=127.0.0.1 \
npm run start:http
# Local HTTP only, without a service-to-service secret. Always binds 127.0.0.1.
# A non-loopback MCP_HTTP_HOST is overridden and that override is logged.
MCP_ALLOW_INSECURE_DEV=1 npm run start:http/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.
docker build -t rootly-mcp .
docker run \
-e CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" \
-p 127.0.0.1:8080:8080 \
rootly-mcpDo 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.
CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" docker compose upSingle-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses ROOTLY_API_TOKEN:
docker run \
-e CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" \
-e AUTH_MODE=env \
-e ROOTLY_API_TOKEN=your_token \
-e MCP_HTTP_HOST=0.0.0.0 \
-p 127.0.0.1:8080:8080 \
rootly-mcpConfiguration
Copy .env.example and set the variables below.
Variable | Required | Description |
| For stdio and | Rootly API token (Bearer). Gateway mode does not read this. |
| No |
|
| No |
|
| Yes for HTTP | Service-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder. Compose will not start without it. Never commit a real value. |
| No | Set to exactly |
| No | Bind address when a secret is configured. Unset means |
| No | HTTP port. Defaults to |
| No |
|
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.
X-Gateway-S2S: t=1710000000,v1=<64 lowercase hex chars>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.
curl -sS http://127.0.0.1:8080/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-H "x-gateway-s2s: $X_GATEWAY_S2S" \
-H "x-rootly-api-token: $ROOTLY_API_TOKEN" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"rootly_status","arguments":{}}}'mcporter Configuration
{
"rootly": {
"command": "node",
"args": ["/path/to/rootly-mcp/dist/index.js"],
"env": {
"ROOTLY_API_TOKEN": "rootly_xxxxxxxxxxxxxxxx"
}
}
}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:
{
"mcpServers": {
"rootly": {
"command": "node",
"args": ["/path/to/rootly-mcp/dist/index.js"],
"env": { "ROOTLY_API_TOKEN": "your_token" }
}
}
}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/v1Auth:
Authorization: Bearer <token>Write content-type:
application/vnd.api+json
Development
npm run dev # watch mode
npm run lint # TypeScript type-check
npm run test # run testsLicense
Apache-2.0 © WYRE Technology
This server cannot be deployed
Maintenance
Related MCP Connectors
- SupabaseOAuthcom.supabase
MCP server for interacting with the Supabase platform
Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.
MCP server for Statsig API - interact with Statsig's feature flags, experiments, and analytics
Related MCP Servers
AlicenseCqualityAmaintenanceManage incidents from your IDE. An MCP server allowing to pull out incidents and their associated metadata using Rootly API.27880 PyPI45Apache 2.0
OpsLevel MCPofficial
AlicenseNot gradedqualityFmaintenanceModel Context Protocol (MCP) server for OpsLevel12MIT- FlicenseNot gradedqualityNot gradedmaintenanceA remote MCP server that provides AI agents access to the Rootly API for incident management, allowing users to query and manage incidents, alerts, teams, services, and other incident management resources through natural language.-
- AlicenseCqualityCmaintenanceIncident Triage MCP is a Model Context Protocol (MCP) server for incident triage. It provides safe, auditable tools for evidence retrieval, deterministic summaries, ticket workflows, and notifications.28Apache 2.0