Rootly▌

# Rootly MCP Server [](https://pypi.org/project/rootly-mcp-server/) [](https://pypi.org/project/rootly-mcp-server/) [](https://pypi.org/project/rootly-mcp-server/) [](https://cursor.com/install-mcp?name=rootly&config=eyJ1cmwiOiJodHRwczovL21jcC5yb290bHkuY29tL3NzZSIsImhlYWRlcnMiOnsiQXV0aG9yaXphdGlvbiI6IkJlYXJlciA8WU9VUl9ST09UTFlfQVBJX1RPS0VOPiJ9fQ==) An MCP server for the [Rootly API](https://docs.rootly.com/api-reference/overview) that integrates seamlessly with MCP-compatible editors like Cursor, Windsurf, and Claude. Resolve production incidents in under a minute without leaving your IDE.  ## Prerequisites - Python 3.12 or higher - `uv` package manager ```bash curl -LsSf https://astral.sh/uv/install.sh | sh ``` - [Rootly API token](https://docs.rootly.com/api-reference/overview#how-to-generate-an-api-key%3F) with appropriate permissions (see below) ### API Token Permissions The MCP server requires a Rootly API token. Choose the appropriate token type based on your needs: - **Global API Key** (Recommended): Full access to all entities across your Rootly instance. Required for organization-wide visibility across teams, schedules, and incidents. - **Team API Key**: Team Admin permissions with full read/edit access to entities owned by that team. Suitable for team-specific workflows. - **Personal API Key**: Inherits the permissions of the user who created it. Works for individual use cases but may have limited visibility. For full functionality of tools like `get_oncall_handoff_summary`, `get_oncall_shift_metrics`, and organization-wide incident search, a **Global API Key** is recommended. ## Quick Start The fastest way to get started is to connect to our hosted MCP server — no installation required. ### Hosted (Streamable HTTP, recommended) ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` ### Hosted (SSE, backward compatible) ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/sse", "headers": { "Authorization": "Bearer " } } } } ``` For **Claude Desktop**, if direct `url` config causes launch issues on your build, use this fallback: ```json { "mcpServers": { "rootly": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.rootly.com/sse", "--transport", "sse-only", "--header", "Authorization: Bearer " ] } } } ``` For **Claude Code**, run: ```bash claude mcp add rootly --transport http https://mcp.rootly.com/mcp \ --header "Authorization: Bearer YOUR_ROOTLY_API_TOKEN" ``` SSE fallback: ```bash claude mcp add rootly-sse --transport sse https://mcp.rootly.com/sse \ --header "Authorization: Bearer YOUR_ROOTLY_API_TOKEN" ``` For **Gemini CLI**, install the extension: ```bash gemini extensions install https://github.com/Rootly-AI-Labs/Rootly-MCP-server ``` Or configure manually in `~/.gemini/settings.json`: ```json { "mcpServers": { "rootly": { "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"], "env": { "ROOTLY_API_TOKEN": "" } } } } ``` ## Alternative Installation (Local) If you prefer to run the MCP server locally, configure your editor with one of the options below. The package will be automatically downloaded and installed when you first open your editor. ### With uv ```json { "mcpServers": { "rootly": { "command": "uv", "args": [ "tool", "run", "--from", "rootly-mcp-server", "rootly-mcp-server" ], "env": { "ROOTLY_API_TOKEN": "" } } } } ``` ## Self-Hosted Transport Options Choose one transport per server process: - **Streamable HTTP** endpoint path: `/mcp` - **SSE** endpoint path: `/sse` Example Docker run (Streamable HTTP): ```bash docker run -p 8000:8000 \ -e ROOTLY_TRANSPORT=streamable-http \ -e ROOTLY_API_TOKEN= \ rootly-mcp-server ``` Example Docker run (SSE): ```bash docker run -p 8000:8000 \ -e ROOTLY_TRANSPORT=sse \ -e ROOTLY_API_TOKEN= \ rootly-mcp-server ``` ### With uvx ```json { "mcpServers": { "rootly": { "command": "uvx", "args": [ "--from", "rootly-mcp-server", "rootly-mcp-server" ], "env": { "ROOTLY_API_TOKEN": "" } } } } ``` ## Features - **Dynamic Tool Generation**: Automatically creates MCP resources from Rootly's OpenAPI (Swagger) specification - **Smart Pagination**: Defaults to 10 items per request for incident endpoints to prevent context window overflow - **API Filtering**: Limits exposed API endpoints for security and performance - **Intelligent Incident Analysis**: Smart tools that analyze historical incident data - **`find_related_incidents`**: Uses TF-IDF similarity analysis to find historically similar incidents - **`suggest_solutions`**: Mines past incident resolutions to recommend actionable solutions - **MCP Resources**: Exposes incident and team data as structured resources for easy AI reference - **Intelligent Pattern Recognition**: Automatically identifies services, error types, and resolution patterns - **On-Call Health Integration**: Detects workload health risk in scheduled responders ## Supported Tools The default server configuration currently exposes **99 tools** (including custom agentic tools and OpenAPI-generated tools). ### Custom Agentic Tools - `check_oncall_health_risk` - `check_responder_availability` - `create_override_recommendation` - `find_related_incidents` - `get_alert_by_short_id` - `get_oncall_handoff_summary` - `get_oncall_schedule_summary` - `get_oncall_shift_metrics` - `get_server_version` - `get_shift_incidents` - `list_endpoints` - `list_shifts` - `search_incidents` - `suggest_solutions` ### OpenAPI-Generated Tools ```text attachAlert createAlert createEnvironment createEscalationLevel createEscalationLevelPaths createEscalationPath createEscalationPolicy createFunctionality createIncidentActionItem createIncidentType createOnCallRole createOnCallShadow createOverrideShift createSchedule createScheduleRotation createScheduleRotationActiveDay createScheduleRotationUser createService createSeverity createTeam createWorkflow deleteEscalationLevel deleteEscalationPath deleteEscalationPolicy deleteSchedule deleteScheduleRotation getAlert getCurrentUser getEnvironment getEscalationLevel getEscalationPath getEscalationPolicy getFunctionality getIncidentType getOnCallRole getOnCallShadow getOverrideShift getSchedule getScheduleRotation getScheduleShifts getService getSeverity getTeam getUser getWorkflow listAlerts listEnvironments listEscalationLevels listEscalationLevelsPaths listEscalationPaths listEscalationPolicies listFunctionalities listIncidentActionItems listIncidentAlerts listIncident_Types listOnCallRoles listOnCallShadows listOverrideShifts listScheduleRotationActiveDays listScheduleRotationUsers listScheduleRotations listSchedules listServices listSeverities listShifts listTeams listUsers listWorkflows updateAlert updateEnvironment updateEscalationLevel updateEscalationPath updateEscalationPolicy updateFunctionality updateIncidentType updateOnCallRole updateOnCallShadow updateOverrideShift updateSchedule updateScheduleRotation updateService updateSeverity updateTeam updateUser updateWorkflow ``` Delete operations are intentionally scoped to screenshot coverage paths: `deleteSchedule`, `deleteScheduleRotation`, `deleteEscalationPolicy`, `deleteEscalationPath`, `deleteEscalationLevel`. ## On-Call Health Integration Rootly MCP integrates with [On-Call Health](https://oncallhealth.ai) to detect workload health risk in scheduled responders. ### Setup Set the `ONCALLHEALTH_API_KEY` environment variable: ```json { "mcpServers": { "rootly": { "command": "uvx", "args": ["rootly-mcp-server"], "env": { "ROOTLY_API_TOKEN": "your_rootly_token", "ONCALLHEALTH_API_KEY": "och_live_your_key" } } } } ``` ### Usage ``` check_oncall_health_risk( start_date="2026-02-09", end_date="2026-02-15" ) ``` Returns at-risk users who are scheduled, recommended safe replacements, and action summaries. ## Example Skills Want to get started quickly? We provide pre-built Claude Code skills that showcase the full power of the Rootly MCP server: ### 🚨 [Rootly Incident Responder](examples/skills/rootly-incident-responder.md) An AI-powered incident response specialist that: - Analyzes production incidents with full context - Finds similar historical incidents using ML-based similarity matching - Suggests solutions based on past successful resolutions - Coordinates with on-call teams across timezones - Correlates incidents with recent code changes and deployments - Creates action items and remediation plans - Provides confidence scores and time estimates **Quick Start:** ```bash # Copy the skill to your project mkdir -p .claude/skills cp examples/skills/rootly-incident-responder.md .claude/skills/ # Then in Claude Code, invoke it: # @rootly-incident-responder analyze incident #12345 ``` This skill demonstrates a complete incident response workflow using Rootly's intelligent tools combined with GitHub integration for code correlati ---