Rootly MCP server

Rootly MCP Server

An MCP server for Rootly API that you can plug into your favorite MCP-compatible editors like Cursor, Windsurf, and Claude. Resolve production incidents in under a minute without leaving your IDE.

Demo GIF

Prerequisites

Python 3.12 or higher
uv package manager
curl -LsSf https://astral.sh/uv/install.sh | sh
Rootly API token

Run it in your IDE

Install with our PyPi package or by cloning this repo.

To set it up in your favorite MCP-compatible editor (we tested it with Cursor and Windsurf), here is the config :

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

If you want to customize allowed_paths to access more Rootly API paths, clone the package and use this config.

{
  "mcpServers": {
    "rootly": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/path/to/rootly-mcp-server",
        "rootly-mcp-server"
      ],
      "env": {
        "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
      }
    }
  }
}

Features

This server dynamically generates MCP resources based on Rootly's OpenAPI (Swagger) specification:

Dynamically generated MCP tools based on Rootly's OpenAPI specification
Default pagination (10 items) for incident endpoints to prevent context window overflow
Limits the number of API paths exposed to the AI agent

Whitelisted Endpoints

By default, the following Rootly API endpoints are exposed to the AI agent (see allowed_paths in src/rootly_mcp_server/server.py):

/v1/incidents
/v1/incidents/{incident_id}/alerts
/v1/alerts
/v1/alerts/{alert_id}
/v1/severities
/v1/severities/{severity_id}
/v1/teams
/v1/teams/{team_id}
/v1/services
/v1/services/{service_id}
/v1/functionalities
/v1/functionalities/{functionality_id}
/v1/incident_types
/v1/incident_types/{incident_type_id}
/v1/incident_action_items
/v1/incident_action_items/{incident_action_item_id}
/v1/incidents/{incident_id}/action_items
/v1/workflows
/v1/workflows/{workflow_id}
/v1/workflow_runs
/v1/workflow_runs/{workflow_run_id}
/v1/environments
/v1/environments/{environment_id}
/v1/users
/v1/users/{user_id}
/v1/users/me
/v1/status_pages
/v1/status_pages/{status_page_id}

We limited the number of API paths exposed for 2 reasons:

Context size: because Rootly's API is very rich in paths, AI agents can get overwhelmed and not perform simple actions properly.
Security: if you want to limit the type of information or actions that users can access through the MCP server

If you want to make more paths available, edit the variable allowed_paths in src/rootly_mcp_server/server.py.

About the Rootly AI Labs

This project was developed by the Rootly AI Labs. The AI Labs is building the future of system reliability and operational excellence. We operate as an open-source incubator, sharing ideas, experimenting, and rapidly prototyping. We're committed to ensuring our research benefits the entire community. Rootly AI logo

Developer Setup & Troubleshooting

1. Install dependencies with `uv`

This project uses uv for fast dependency management. To install all dependencies from your pyproject.toml:

uv pip install .

2. Using a virtual environment

It is recommended to use a virtual environment for development:

uv venv .venv
source .venv/bin/activate

3. Running the test client

To run the test client and verify your setup:

python test_mcp_client.py

5. General tips

Always activate your virtual environment before running scripts.
If you add new dependencies, use uv pip install <package> to keep your environment up to date.
If you encounter issues, check your Python version and ensure it matches the project's requirements.

6. Connecting to Our MCP Server

You can configure your client to connect directly to our 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>"
      }
    }
  }
}

This server cannot be installed

security - not tested

license - permissive license

quality - not tested

remote-capable server

The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.

Manage incidents from your IDE. An MCP server allowing to pull out incidents and their associated metadata using Rootly API.

Related Resources

Reddit Discussion about this server

Related MCP Servers

mcp-server-datadog
winor30
A
security
A
license
A
quality
The MCP server provides an interface to the Datadog API, enabling seamless management of incidents, monitoring, logs, dashboards, metrics, traces, and hosts. Its extensible design allows easy integration of additional Datadog APIs for future expansions.
Last updated -
14
322
36
TypeScript
Apache 2.0
Unstructured API MCP Serverofficial
Unstructured-IO
A
security
F
license
A
quality
An MCP server implementation that enables interaction with the Unstructured API, providing tools to list, create, update, and manage sources, destinations, and workflows.
Last updated -
39
26
EventCatalog MCP Serverofficial
event-catalog
-
security
F
license
-
quality
A server that connects MCP clients (Claude, Cursor, Windsurf, etc.) to EventCatalog instances, allowing users to ask questions about their event-driven architecture and get insights about domains, services, and message schemas directly within their development tools.
Last updated -
21
13
TypeScript
MCP LLMS-TXT Documentation Server
langchain-ai
-
security
A
license
-
quality
An MCP server that provides tools to load and fetch documentation from any llms.txt source, giving users full control over context retrieval for LLMs in IDE agents and applications.
Last updated -
177
Python
MIT License

View all related MCP servers

Rootly MCP server