Back to Browse

Rootly MCP Server

Developer ToolsModerate6.6MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

About

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

Security Report

6.6
Moderate6.6Moderate Risk

The rootly-mcp server demonstrates solid security practices with proper API token authentication via environment variables, no hardcoded credentials, and appropriate permission scoping for its incident management purpose. The server uses the official MCP SDK and legitimate dependencies. Minor code quality concerns around broad exception handling and the embedded UI bundle do not significantly impact security. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 1 high severity).

3 files analyzed · 5 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Rootly API token (Bearer credential)Required

Environment variable: ROOTLY_API_TOKEN

Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.Optional

Environment variable: MCP_TRANSPORT

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.Optional

Environment variable: AUTH_MODE

Log verbosity: debug, info, warn, errorOptional

Environment variable: LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-wyre-ai-rootly-mcp": {
      "env": {
        "AUTH_MODE": "your-auth-mode-here",
        "LOG_LEVEL": "your-log-level-here",
        "MCP_TRANSPORT": "your-mcp-transport-here",
        "ROOTLY_API_TOKEN": "your-rootly-api-token-here"
      },
      "args": [
        "-y",
        "@wyre-ai/rootly-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

cd rootly-mcp
npm install
npm run build

2. Set your API token

export ROOTLY_API_TOKEN=rootly_xxxxxxxxxxxxxxxx

Get your token from Rootly → Profile → API Tokens.

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

ROOTLY_API_TOKEN=your_token node dist/index.js

4. Run (HTTP streaming transport)

ROOTLY_API_TOKEN=your_token MCP_TRANSPORT=http node dist/http.js
# Listens on :8080 — /mcp for MCP, /health for health check

5. Run with Docker

docker compose up
# or
docker run -e ROOTLY_API_TOKEN=your_token ghcr.io/wyre-ai/rootly-mcp:latest

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

Development

npm run dev        # watch mode
npm run lint       # TypeScript type-check
npm run test       # run tests

License

Apache-2.0 © WYRE Technology

Reviews

No reviews yet

Be the first to review this server!