# Rootly-AI-Labs/Rootly-MCP-server [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/Rootly-AI-Labs/Rootly-MCP-server  
**GitHub Stars:** 45  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rootly-ai-labs-rootly-mcp-server

## Description
MCP server for the incident management platform Rootly.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

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

**Requires environment variables:** `ROOTLY_API_TOKEN`, `ROOTLY_MCP_ENABLE_WRITE_TOOLS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Rootly-AI-Labs/Rootly-MCP-server does

Rootly-AI-Labs/Rootly-MCP-server gives MCP clients access to Rootly’s incident management API. Its scope includes incidents, alerts, services, and on-call operations, allowing an agent to retrieve Rootly data and perform supported API actions from an MCP conversation.

The hosted service is intended for clients that can connect to a remote MCP endpoint. A local package is also available for deployments that need the server process to run in their own environment.

## How it works

The recommended hosted endpoint uses Streamable HTTP at `https://mcp.rootly.com/mcp`. Clients can authenticate through an OAuth2 login flow, or send a Rootly API token as a bearer token. Code Mode is available at `https://mcp.rootly.com/mcp-codemode`.

Hosted connections support a full tool profile and a slim profile of roughly 70 tools. The slim profile can be selected with the `tool_profile=slim` query parameter or the `X-Rootly-Tool-Profile: slim` header. An exact enabled-tool selection can also be configured through the hosted service.

The older SSE endpoint remains available only as a migration path and is scheduled for removal after November 20, 2026. New configurations should use Streamable HTTP or Code Mode instead.

## Setup and configuration

The simplest setup adds the hosted MCP URL to a client configuration. OAuth2 is the recommended authentication method for hosted use; the client opens a browser so the user can sign in to Rootly. Token-based setups send `Authorization: Bearer YOUR_ROOTLY_API_TOKEN`.

For local execution, the package requires Python 3.12 or newer and the `uv` package manager. Start it with the `rootly-mcp-server` package and provide `ROOTLY_API_TOKEN`. Write operations are enabled by setting `ROOTLY_MCP_ENABLE_WRITE_TOOLS` to `true`.

Rootly supports global, team, and personal API keys. Global keys provide organization-wide access and are recommended for queries or changes spanning multiple teams, schedules, or incidents. The hosted service can also be registered in Databricks Unity Gateway.

## Tools and capabilities

- Query and manage Rootly incidents.
- Work with alerts and services.
- Access on-call operations and related scheduling data.
- Connect through hosted Streamable HTTP, Code Mode, or local execution.
- Choose between full, slim, or explicitly selected hosted tool sets.
- Expose the hosted tools to Databricks agents through Unity Gateway.

The full hosted profile exposes about 250 tools when loaded through the Databricks integration. Tool selection in Unity Gateway can restrict the set made available to agents.

## Limitations and notes

Write access depends on both the available tools and the permissions of the Rootly API credential. Team and personal keys may limit visibility or actions compared with a global key. SSE is deprecated, including the self-hosted SSE transport, and should be replaced with Streamable HTTP before its removal date.

_Full upstream README: https://allmcps.com/mcp/rootly-ai-labs-rootly-mcp-server/readme_