Rootly MCP server
{
"mcpServers": {
"rootly": {
"type": "http",
"url": "https://mcp.rootly.com/mcp-codemode"
}
}
}{
"mcpServers": {
"rootly": {
"type": "http",
"url": "https://mcp.rootly.com/mcp-codemode"
}
}
}{
"mcpServers": {
"rootly": {
"type": "http",
"url": "https://mcp.rootly.com/mcp-codemode"
}
}
}{
"servers": {
"rootly": {
"type": "http",
"url": "https://mcp.rootly.com/mcp-codemode"
}
}
}{
"mcpServers": {
"rootly": {
"type": "http",
"url": "https://mcp.rootly.com/mcp-codemode"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall uvx rootly-mcp-serverversion 2.2.4
What it does
An MCP server that exposes the Rootly API for incident management, on-call scheduling, and incident analysis. It works with Cursor, Windsurf, Claude, and other MCP clients via hosted endpoints or local installation.
- Create and update incidents, search incidents by status or severity, and track incident timelines from your development environment.
- Manage on-call schedules, view who is on call, and make schedule adjustments programmatically.
- Analyze incidents and generate insights using Rootly's intelligent analysis features.
Tools this server exposes
| Tool | Does |
|---|---|
| incident_create | Create a new incident in Rootly. |
| incident_update | Update an existing incident. |
| incident_search | Search for incidents by status, severity, or other criteria. |
| incident_get | Retrieve details of a specific incident. |
| on_call_schedule_list | List on-call schedules. |
| on_call_get_current | Get the current on-call person for a schedule. |
| service_list | List services in Rootly. |
| alert_list | List alerts. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.