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

AI-generated 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.
Before you install
The Rootly API token is a bearer credential granting access to incident data; keep it out of logs and repositories. Many tools write: creating, updating and resolving incidents and alerts, and acknowledging alerts. Rootly limits writes to 3 per 60 seconds, so bulk changes will fail. HTTP mode requires CONDUIT_S2S_SECRET and refuses placeholder values; the insecure dev bypass disables request authentication and should stay local. Incident data is sent to the Rootly API.

Installation

In SourceWeft

  1. Open Rootly in the dashboard and add it to a workspace.
  2. 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)

ToolDescription
rootly_navigateNavigate to a domain: incidents, alerts, schedules, org
rootly_statusCheck connection status and available domains
rootly_backReturn to the navigation menu

Domain: incidents

ToolDescription
rootly_incidents_listList incidents with optional status/severity filters
rootly_incidents_getGet a single incident by ID
rootly_incidents_createCreate a new incident
rootly_incidents_updateUpdate title, summary, status, or severity
rootly_incidents_resolveResolve an incident

Domain: alerts

ToolDescription
rootly_alerts_listList alerts with optional status filter
rootly_alerts_acknowledgeAcknowledge an alert
rootly_alerts_resolveResolve an alert
rootly_alerts_createCreate a new alert
rootly_alerts_updateUpdate alert status or summary

Domain: schedules

ToolDescription
rootly_schedules_listList on-call schedules
rootly_schedules_getGet a single on-call schedule

Domain: org

ToolDescription
rootly_org_list_teamsList teams
rootly_org_list_severitiesList severity levels
rootly_org_current_userGet current authenticated user

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

bash
cd rootly-mcpnpm installnpm run build

2. Set your API token

bash
export ROOTLY_API_TOKEN=rootly_xxxxxxxxxxxxxxxx

Get your token from Rootly → Profile → API Tokens.

3. Run (stdio — for mcporter/Claude Desktop)

bash
ROOTLY_API_TOKEN=your_token node dist/index.js

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.

bash
# 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.

bash
docker build -t rootly-mcp .docker run \  -e CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" \  -p 127.0.0.1:8080:8080 \  rootly-mcp

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.

bash
CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" docker compose up

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses ROOTLY_API_TOKEN:

bash
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-mcp

Configuration

Copy .env.example and set the variables below.

VariableRequiredDescription
ROOTLY_API_TOKENFor stdio and AUTH_MODE=envRootly API token (Bearer). Gateway mode does not read this.
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENogateway (Docker image and Compose default) or env. Gateway mode requires X-Rootly-Api-Token on each /mcp request and never falls back to ROOTLY_API_TOKEN. env uses that variable after S2S auth succeeds.
CONDUIT_S2S_SECRETYes for HTTPService-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.
MCP_ALLOW_INSECURE_DEVNoSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST is overridden and logged. A placeholder secret still refuses to start.
MCP_HTTP_HOSTNoBind address when a secret is configured. Unset means 0.0.0.0. The container image sets 0.0.0.0. Ignored in favor of 127.0.0.1 when the insecure-dev bypass is on.
MCP_HTTP_PORTNoHTTP port. Defaults to 8080.
LOG_LEVELNodebug, info, warn, or error. Defaults to info.

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.

bash
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

json
{  "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:

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

Development

bash
npm run dev        # watch modenpm run lint       # TypeScript type-checknpm run test       # run tests

License

Apache-2.0 © WYRE Technology

Source: README.md at commit 514e44d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v1.2.9LatestOct 14, 2026
  2. v1.2.8Oct 13, 2026
  3. v1.2.7Oct 9, 2026
  4. 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