Skip to content
Rootly

RootlyMCP Server

by Rootly
Released
v2.2.4
Apache-2.0
Repository Docs
Cloud & Infrastructure

Summary

Rootly's official MCP server for incident management and on-call — declare and update incidents, page the right responder, and pull timelines and retrospectives into an agent session.

Features

  • Declare, update and resolve incidents with severity, status and timeline events
  • Read on-call schedules and page the responder on duty
  • Pull alerts, retrospectives and post-incident action items into the agent session
  • Hosted endpoints: streamable HTTP, SSE and Code Mode, with OAuth 2.1 and no local install
  • Tool profiles (full / slim ~70 tools / explicit allowlist) to keep the context window manageable

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Rootly" tools will be available.
{
  "mcpServers": {
    "rootly-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "rootly-mcp-server",
        "rootly-mcp-server"
      ],
      "env": {
        "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
      }
    }
  }
}

Description

Rootly is an incident-management and on-call platform, and its official MCP server puts the Rootly API in front of an agent so the parts of an incident that are pure coordination stop needing a human in a browser tab.

In practice that means declaring an incident and setting its severity, updating status and adding timeline events as work proceeds, reading who is on call and paging them, pulling alerts and their grouping, and reading back retrospectives and post-incident action items. Because the tools follow the Rootly REST API, an agent already sitting in the repository that caused the incident can annotate the timeline with the commit and the rollback without leaving the terminal.

The hosted server is the recommended path and needs no local install. https://mcp.rootly.com/mcp speaks streamable HTTP, /sse remains as a stable alternative, and /mcp-codemode exposes the same surface in Code Mode. OAuth 2.1 is the default — the client opens a browser and no API token is stored anywhere — with a Authorization: Bearer token as the fallback for headless setups.

The Rootly API is large enough that the full tool list can crowd a context window, so the server ships tool profiles: append ?tool_profile=slim (or send X-Rootly-Tool-Profile: slim) for a roughly 70-tool subset, or pin an exact list with ROOTLY_MCP_ENABLED_TOOLS. A local stdio build is published to PyPI as rootly-mcp-server and runs under uvx for teams that will not route through a hosted endpoint. Apache-2.0 licensed, maintained by Rootly AI Labs.

Related MCP Servers

MCP: PagerDuty MCP

by PagerDuty

PagerDuty's official MCP server with 80+ tools for incidents, schedules, services and escalation policies — read-only by default, with write actions behind an explicit flag.

Developer Tools

MCP: Checkly MCP Server

by Checkly

Checkly's hosted MCP server gives an agent read access to your synthetic monitoring account — check health, failing results, test sessions, Rocky AI root-cause analyses, incidents and status pages — over streamable HTTP with OAuth.

Cloud & Infrastructure

MCP: Dagster+ MCP Server

by Dagster Labs

Dagster Labs' official remote MCP server for Dagster+: inspect assets, runs, run logs and Insights metrics, and launch runs from an AI session.

Databases & Data
Browse all MCP servers →