Rootly

You can run the Rootly MCP Server to connect your MCP-compatible editors to Rootly’s incident data. It exposes incident and team data as MCP resources, generates tools dynamically from Rootly’s API, and includes on-call health integration to help you resolve production incidents quickly from your editor.

How to use

You will configure your MCP client to connect to either a locally running MCP server or a hosted server. The hosted option lets you join Rootly’s MCP endpoint directly, while local options run the server on your machine via a small runtime tool. Choose the connection method that fits your workflow and keep your API tokens secure.

How to install

Prerequisites: You need Python 3.12 or higher installed on your system.

Install the uv package manager if you plan to run a local MCP server through the uv runtime.

Install and configure your Rootly API access token or keys as shown in the examples. These tokens authorize access to incident data and on-call information.

{
  "mcpServers": {
    "rootly": {
      "command": "uv",
      "args": [
        "tool",
        "run",
        "--from",
        "rootly-mcp-server",
        "rootly-mcp-server"
      ],      
      "env": {
        "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
      }
    }
  }
}

Additional installation and startup options

If you prefer a hosted MCP server, you can connect directly using the hosted endpoint. This avoids running the server locally but requires your Rootly API token for authentication.

Configuration examples and connection methods

Three explicit MCP connection methods are supported in this setup. The HTTP method connects to a hosted MCP server, while the stdio methods run locally using uv or uvx.

HTTP hosted MCP server

{
  "mcpServers": {
    "rootly": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.rootly.com/sse",
        "--header",
        "Authorization:${ROOTLY_AUTH_HEADER}"
      ],
      "env": {
        "ROOTLY_AUTH_HEADER": "Bearer <YOUR_ROOTLY_API_TOKEN>"
      }
    }
  }
}

Local runtime with uv

{
  "mcpServers": {
    "rootly": {
      "command": "uv",
      "args": [
        "tool",
        "run",
        "--from",
        "rootly-mcp-server",
        "rootly-mcp-server"
      ],      
      "env": {
        "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
      }
    }
  }
}

Local runtime with uvx and optional On-Call Health integration

{
  "mcpServers": {
    "rootly": {
      "command": "uvx",
      "args": [
        "--from",
        "rootly-mcp-server",
        "rootly-mcp-server"
      ],      
      "env": {
        "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>",
        "ONCALLHEALTH_API_KEY": "och_live_your_key"
      }
    }
  }
}

Available tools

Dynamic MCP resource generation

Automatically creates MCP resources from Rootly's OpenAPI specification, enabling editors to access incidents and teams.

Smart pagination

Defaults to 10 items per request for incident endpoints to prevent context window overflow.

API filtering

Limits exposed API endpoints for security and performance.

find_related_incidents

TF-IDF based similarity analysis to locate historically similar incidents.

suggest_solutions

Mining past incident resolutions to recommend actionable fixes.

oncall_health_integration

Detects workload health risk in scheduled responders and suggests mitigations.