Rootly MCP Server: Seamless Sync & Unmatched Scalability

Rootly MCP Server: Mirror configurations flawlessly, sync environments seamlessly, and unlock unmatched scalability. The future of reliable ops, mirrored in real-time!

Visit Repository

✨ Developer Tools

4.9(148 reviews)

222 saves

103 comments

49% of users reported increased productivity after just one week

About Rootly MCP Server

What is Rootly MCP Server: Seamless Sync & Unmatched Scalability?

Rootly MCP Server is a bridge between Rootly's incident management API and MCP-compatible development tools like Cursor and Windsurf. It enables real-time synchronization of production incident data directly within your IDE, eliminating context-switching. For example, developers can view active alerts or trigger remediation actions without leaving their code editor, accelerating incident resolution by up to 90% in testing environments.

How to Use Rootly MCP Server: Seamless Sync & Unmatched Scalability?

Installation requires Python 3.12+ and the uv package manager. First configure your environment with:

curl -LsSf https://astral.sh/uv/install.sh | sh

Then setup in your editor with this config snippet:


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

Advanced users can customize exposed API endpoints by modifying allowed_paths in the server configuration.

Rootly MCP Server Features

Key Features of Rootly MCP Server: Seamless Sync & Unmatched Scalability?

Adaptive API Integration: Automatically generates MCP tools from Rootly's OpenAPI spec, supporting new API versions without manual updates
Context Optimization: Default 10-item pagination for incident streams prevents LLM context overflow during analysis
Security Layers: Whitelisted API paths restrict access to sensitive operations - currently limited to incidents and alert streams

These safeguards ensure safe AI-driven operations while maintaining performance - for example, limiting API exposure prevents accidental deletion of critical incident records.

Use Cases of Rootly MCP Server: Seamless Sync & Unmatched Scalability?

Teams use this server to:

Trigger auto-remediation workflows directly from code diffs
Create real-time incident dashboards within editor sidebars
Automate SRE playbooks through editor-based AI suggestions

Rootly MCP Server FAQ

FAQ from Rootly MCP Server: Seamless Sync & Unmatched Scalability?

Q: Is this compatible with VS Code?: Yes, through MCP extensions like Windmill. Full compatibility list available in our API docs
Q: Can I expose custom API endpoints?: Yes - edit allowed_paths in server.py to include paths like /services for infrastructure correlation
Q: Is this ready for production?: Currently a prototype, but includes rate-limiting and token scopes. Production-ready version planned Q3 2024
Q: How does pagination work?: Returns 10 items by default, with page and per_page parameters for manual override

Content

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

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. As of now we only expose the /incidents and /incidents/{incident_id}/alerts.
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 path available, edit the variable allowed_paths in src/rootly_mcp_server/server.py.

Disclaimer

This project is a prototype and not intended for production use. If you have featured ideas or spotted some issues, feel free to submit a PR or open an issue.

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