Skip to main content
ClaudeWave

MCP server for the Rootly incident management platform — alerts, incidents, on-call schedules

MCP ServersRegistry oficial0 estrellas0 forksTypeScriptNOASSERTIONActualizado yesterday
ClaudeWave Trust Score
80/100
Trusted
Passed
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Flags
  • !Licence file present but not machine-readable
Last scanned: 8/27/2026
Install in Claude Code / Claude Desktop
Method: Docker · ghcr.io/wyre-ai/rootly-mcp
Claude Code CLI
claude mcp add rootly-mcp -- docker run -i --rm ghcr.io/wyre-ai/rootly-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "rootly-mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/wyre-ai/rootly-mcp"],
      "env": {
        "ROOTLY_API_TOKEN": "<rootly_api_token>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Detected environment variables
ROOTLY_API_TOKEN
Casos de uso

Resumen de MCP Servers

# rootly-mcp

MCP server for the [Rootly](https://rootly.com) incident management platform.

Built by WYRE Technology — part of the wyre-projects MCP server collection.

Uses **decision-tree navigation**: start with `rootly_navigate` to select a domain, then use that domain's tools. Call `rootly_back` to return.

## Domains & Tools

### Navigation (always available)
| Tool | Description |
|------|-------------|
| `rootly_navigate` | Navigate to a domain: `incidents`, `alerts`, `schedules`, `org` |
| `rootly_status` | Check connection status and available domains |
| `rootly_back` | Return to the navigation menu |

### Domain: incidents
| Tool | Description |
|------|-------------|
| `rootly_incidents_list` | List incidents with optional status/severity filters |
| `rootly_incidents_get` | Get a single incident by ID |
| `rootly_incidents_create` | Create a new incident |
| `rootly_incidents_update` | Update title, summary, status, or severity |
| `rootly_incidents_resolve` | Resolve an incident |

### Domain: alerts
| Tool | Description |
|------|-------------|
| `rootly_alerts_list` | List alerts with optional status filter |
| `rootly_alerts_acknowledge` | Acknowledge an alert |
| `rootly_alerts_resolve` | Resolve an alert |
| `rootly_alerts_create` | Create a new alert |
| `rootly_alerts_update` | Update alert status or summary |

### Domain: schedules
| Tool | Description |
|------|-------------|
| `rootly_schedules_list` | List on-call schedules |
| `rootly_schedules_get` | Get a single on-call schedule |

### Domain: org
| Tool | Description |
|------|-------------|
| `rootly_org_list_teams` | List teams |
| `rootly_org_list_severities` | List severity levels |
| `rootly_org_current_user` | Get current authenticated user |

## Interactive Incident Card (MCP Apps)

`rootly_incidents_get` renders as an interactive read-only card in MCP Apps
hosts (Claude Desktop/web) showing status, severity, services, environments,
teams, and a lifecycle timeline; plain-JSON behavior is unchanged in other
hosts. The card is neutral by default and brandable via `window.__BRAND__`
injection or `MCP_BRAND_*` env vars (`MCP_BRAND_NAME`, `MCP_BRAND_LOGO_URL`,
`MCP_BRAND_PRIMARY_COLOR`, `MCP_BRAND_ACCENT_COLOR`, `MCP_BRAND_BG`,
`MCP_BRAND_TEXT`) — no rebuild needed. Rebuild the card bundle itself with
`npm run build:ui` (only needed when `ui/` changes; the embedded output is
committed).

## Setup

### 1. Install & build

```bash
cd rootly-mcp
npm install
npm run build
```

### 2. Set your API token

```bash
export ROOTLY_API_TOKEN=rootly_xxxxxxxxxxxxxxxx
```

Get your token from **Rootly → Profile → API Tokens**.

### 3. Run (stdio — for mcporter/Claude Desktop)

```bash
ROOTLY_API_TOKEN=your_token node dist/index.js
```

### 4. Run (HTTP streaming transport)

```bash
ROOTLY_API_TOKEN=your_token MCP_TRANSPORT=http node dist/http.js
# Listens on :8080 — /mcp for MCP, /health for health check
```

### 5. Run with Docker

```bash
docker compose up
# or
docker run -e ROOTLY_API_TOKEN=your_token ghcr.io/wyre-ai/rootly-mcp:latest
```

## mcporter Configuration

```json
{
  "rootly": {
    "command": "node",
    "args": ["/path/to/rootly-mcp/dist/index.js"],
    "env": {
      "ROOTLY_API_TOKEN": "rootly_xxxxxxxxxxxxxxxx"
    }
  }
}
```

Then: `mcporter call rootly.rootly_navigate --domain alerts`

## Claude Desktop (MCPB)

Download the `.mcpb` bundle from [Releases](https://github.com/WYRE-AI/rootly-mcp/releases) and install it in Claude Desktop.

Or manually add to `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "rootly": {
      "command": "node",
      "args": ["/path/to/rootly-mcp/dist/index.js"],
      "env": { "ROOTLY_API_TOKEN": "your_token" }
    }
  }
}
```

## Rate Limiting

Rootly enforces **3 write operations per 60 seconds**. The server tracks this in-process and returns a descriptive error with retry-after time if exceeded.

## API Reference

- Rootly API docs: <https://docs.rootly.com/api-reference>
- API base URL: `https://api.rootly.com/v1`
- Auth: `Authorization: Bearer <token>`
- Write content-type: `application/vnd.api+json`

## Development

```bash
npm run dev        # watch mode
npm run lint       # TypeScript type-check
npm run test       # run tests
```

## License

Apache-2.0 © WYRE Technology
alertsincidentsmcpmodel-context-protocolmspmsp-mcpon-callrootlywyre-technology

Lo que la gente pregunta sobre rootly-mcp

¿Qué es WYRE-AI/rootly-mcp?

+

WYRE-AI/rootly-mcp es mcp servers para el ecosistema de Claude AI. MCP server for the Rootly incident management platform — alerts, incidents, on-call schedules Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-08-25.

¿Cómo se instala rootly-mcp?

+

Puedes instalar rootly-mcp clonando el repositorio (https://github.com/WYRE-AI/rootly-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar WYRE-AI/rootly-mcp?

+

Nuestro agente de seguridad ha analizado WYRE-AI/rootly-mcp y le ha asignado un Trust Score de 80/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene WYRE-AI/rootly-mcp?

+

WYRE-AI/rootly-mcp es mantenido por WYRE-AI. La última actividad registrada en GitHub es del 2026-08-25, con 2 issues abiertos.

¿Hay alternativas a rootly-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega rootly-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: WYRE-AI/rootly-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/wyre-ai-rootly-mcp)](https://claudewave.com/repo/wyre-ai-rootly-mcp)
<a href="https://claudewave.com/repo/wyre-ai-rootly-mcp"><img src="https://claudewave.com/api/badge/wyre-ai-rootly-mcp" alt="Featured on ClaudeWave: WYRE-AI/rootly-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a rootly-mcp