# Rootly > Incident management, on-call scheduling, and intelligent analysis powered by Rootly. - **Type:** MCP server - **Install:** `agentstack add mcp-rootly-ai-labs-rootly-mcp-server` - **Verified:** Pending review - **Seller:** [rootlyhq](https://agentstack.voostack.com/s/rootlyhq) - **Installs:** 0 - **Category:** [Integrations](https://agentstack.voostack.com/c/integrations) - **Latest version:** 2.2.4 - **License:** Apache-2.0 - **Upstream author:** [rootlyhq](https://github.com/rootlyhq) - **Source:** https://github.com/rootlyhq/rootly-mcp-server - **Website:** https://rootly.com/ai-labs ## Install ```sh agentstack add mcp-rootly-ai-labs-rootly-mcp-server ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Rootly MCP Server [](https://pypi.org/project/rootly-mcp-server/) [](https://pypi.org/project/rootly-mcp-server/) [](https://pypi.org/project/rootly-mcp-server/) An MCP server for the [Rootly API](https://docs.rootly.com/api-reference/overview) for Cursor, Windsurf, Claude, and other MCP clients. ## Quick Start Use the hosted MCP server. No local installation required. ### Hosted Transport Options - **Streamable HTTP (recommended):** `https://mcp.rootly.com/mcp` - **SSE (stable alternative):** `https://mcp.rootly.com/sse` - **Code Mode:** `https://mcp.rootly.com/mcp-codemode` Hosted tool profiles: - **Full (default):** use the URLs above as-is - **Slim (~70 tools):** add `?tool_profile=slim` to the hosted URL, for example `https://mcp.rootly.com/mcp?tool_profile=slim` - **Header alternative:** send `X-Rootly-Tool-Profile: slim` - **Server-wide default:** set `ROOTLY_MCP_HOSTED_TOOL_PROFILE=full|slim` - **Exact custom override:** set `ROOTLY_MCP_ENABLED_TOOLS=...` ### General Remote Setup **With OAuth2 (recommended):** ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } } ``` Your MCP client handles OAuth2 login automatically — a browser window opens for you to authenticate with Rootly. No API token needed. **With API Token:** ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp", "headers": { "Authorization": "Bearer YOUR_ROOTLY_API_TOKEN" } } } } ``` SSE (alternative): ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/sse" } } } ``` Code Mode: ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp-codemode" } } } ``` ### Agent Setup Claude Code **With OAuth2 (recommended):** ```bash claude mcp add --transport http rootly https://mcp.rootly.com/mcp # Code Mode: claude mcp add --transport http rootly-codemode https://mcp.rootly.com/mcp-codemode ``` **With API Token:** ```bash claude mcp add --transport http rootly https://mcp.rootly.com/mcp \ --header "Authorization: Bearer YOUR_ROOTLY_API_TOKEN" ``` **Manual Configuration** — Create `.mcp.json` in your project root: ```json { "mcpServers": { "rootly": { "type": "http", "url": "https://mcp.rootly.com/mcp" } } } ``` Gemini CLI Install the extension: ```bash gemini extensions install https://github.com/rootlyhq/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": "" } } } } ``` Cursor Add to `.cursor/mcp.json` or `~/.cursor/mcp.json`: **With OAuth2 (recommended):** ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } } ``` **With API Token:** ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` Windsurf Add to `~/.codeium/windsurf/mcp_config.json`: **With OAuth2 (recommended):** ```json { "mcpServers": { "rootly": { "serverUrl": "https://mcp.rootly.com/mcp" } } } ``` **With API Token:** ```json { "mcpServers": { "rootly": { "serverUrl": "https://mcp.rootly.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` Codex Add to `~/.codex/config.toml`: **With OAuth2 (recommended):** ```toml [mcp_servers.rootly] url = "https://mcp.rootly.com/mcp" ``` **With API Token:** ```toml [mcp_servers.rootly] url = "https://mcp.rootly.com/mcp" bearer_token_env_var = "ROOTLY_API_TOKEN" ``` Claude Desktop **With OAuth2 (recommended):** Add to `claude_desktop_config.json`: ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } } ``` Claude Desktop handles OAuth2 login automatically. **With API Token (via mcp-remote):** ```json { "mcpServers": { "rootly": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.rootly.com/mcp", "--transport", "http", "--header", "Authorization: Bearer " ] } } } ``` ## Rootly CLI Standalone CLI for incidents, alerts, services, and on-call operations. Install via Homebrew: ```bash brew install rootlyhq/tap/rootly-cli ``` Or via Go: ```bash go install github.com/rootlyhq/rootly-cli/cmd/rootly@latest ``` For more details, see the [Rootly CLI repository](https://github.com/rootlyhq/rootly-cli). ## Alternative Installation (Local) Run the MCP server locally if you do not want to use the hosted service. ### 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) ### API Token Types Choose the token type based on the access you need: - **Global API Key**: Full access across the Rootly instance. Best for organization-wide visibility. - **Team API Key**: Access limited to entities owned by that team. - **Personal API Key**: Access matches the user who created it. A **Global API Key** is recommended for organization-wide queries and for actions that modify data, especially when workflows may span multiple teams, schedules, or incidents. ### With uv ```json { "mcpServers": { "rootly": { "command": "uv", "args": [ "tool", "run", "--from", "rootly-mcp-server", "rootly-mcp-server" ], "env": { "ROOTLY_API_TOKEN": "", "ROOTLY_MCP_ENABLE_WRITE_TOOLS": "true" } } } } ``` ## Self-Hosted Transport Options Choose one transport per server process: - **Streamable HTTP** endpoint path: `/mcp` - **SSE** endpoint path: `/sse` - **Code Mode (experimental)** endpoint path: `/mcp-codemode` in hosted dual-transport mode Hosted and self-hosted deployments now both expose the full tool surface by default. - Hosted default: full surface - Hosted slim profile: about 70 high-usage tools via `?tool_profile=slim` - Self-hosted default: full surface To restrict either deployment to read-only tools, start the server with `--no-enable-write-tools` or set `ROOTLY_MCP_ENABLE_WRITE_TOOLS=false`. For hosted clients that want the smaller remote profile, append `?tool_profile=slim` to the MCP URL or send `X-Rootly-Tool-Profile: slim`. To override the hosted or self-hosted default profile entirely, set `ROOTLY_MCP_ENABLED_TOOLS` (or pass `--enabled-tools`) with a comma-separated allowlist of exact tool names. When that variable is set, it fully replaces the default selection. To expose only a specific subset of MCP tools on a self-hosted deployment, set `ROOTLY_MCP_ENABLED_TOOLS` (or pass `--enabled-tools`) with a comma-separated allowlist of exact tool names, for example `list_incidents,get_incident,get_server_version`. To discover the exact tool names available under your current self-hosted configuration, run: ```bash ROOTLY_API_TOKEN= \ uv run python -m rootly_mcp_server --list-tools ``` This prints the effective MCP tool names after applying your current settings, including `ROOTLY_MCP_ENABLE_WRITE_TOOLS` and `ROOTLY_MCP_ENABLED_TOOLS`. Smoke-test a self-hosted allowlist: ```bash ROOTLY_API_TOKEN= \ ROOTLY_MCP_ENABLED_TOOLS=list_incidents,get_incident,get_server_version \ uv run python -m rootly_mcp_server --transport streamable-http --log-level ERROR ``` Then connect an MCP client to `http://127.0.0.1:8000/mcp` and verify `tools/list` returns only: ```text get_server_version get_incident list_incidents ``` To include specific write tools for self-hosted testing, add both the write flag and the allowlist: ```bash ROOTLY_API_TOKEN= \ ROOTLY_MCP_ENABLE_WRITE_TOOLS=true \ ROOTLY_MCP_ENABLED_TOOLS=create_incident,create_workflow_task,list_teams \ uv run python -m rootly_mcp_server --transport streamable-http --log-level ERROR ``` Example Docker run (Streamable HTTP): ```bash docker run -p 8000:8000 \ -e ROOTLY_TRANSPORT=streamable-http \ -e ROOTLY_API_TOKEN= \ -e ROOTLY_MCP_ENABLE_WRITE_TOOLS=true \ rootly-mcp-server ``` Example Docker run (SSE): ```bash docker run -p 8000:8000 \ -e ROOTLY_TRANSPORT=sse \ -e ROOTLY_API_TOKEN= \ rootly-mcp-server ``` Example Docker run (Dual transport + Code Mode): ```bash docker run -p 8000:8000 \ -e ROOTLY_TRANSPORT=both \ -e ROOTLY_API_TOKEN= \ rootly-mcp-server ``` ## Workflow-Focused Tool Subsets The full hosted and self-hosted surface exposes 200+ tools. If you want tighter workflow-specific subsets, use `ROOTLY_MCP_ENABLED_TOOLS`: ### 🚨 Incident Response (25 tools) *Essential tools for emergency responders and incident commanders* ```bash ROOTLY_MCP_ENABLED_TOOLS="list_incidents,get_incident,create_incident,update_incident,search_incidents,find_related_incidents,suggest_solutions,create_incident_action_item,list_incident_action_items,update_incident_form_field_selection,list_teams,get_current_user,list_services,list_severities,get_alert,list_alerts,get_alert_by_short_id,list_escalation_policies,get_escalation_policy,list_on_call_roles,list_schedules,get_schedule_shifts,get_oncall_handoff_summary,get_shift_incidents,list_endpoints" ``` ### 📅 On-Call Management (35 tools) *For schedule coordinators and on-call managers* ```bash ROOTLY_MCP_ENABLED_TOOLS="list_schedules,get_schedule,update_schedule,get_schedule_shifts,list_shifts,create_schedule_rotation,update_schedule_rotation,list_schedule_rotations,get_schedule_rotation,list_schedule_rotation_users,update_schedule_rotation_user,create_on_call_shadow,update_on_call_shadow,list_on_call_shadows,create_override_shift,update_override_shift,list_override_shifts,list_on_call_roles,update_on_call_role,get_oncall_schedule_summary,get_oncall_shift_metrics,check_oncall_health_risk,check_responder_availability,create_override_recommendation,list_teams,get_team,list_users,get_user,get_current_user,list_escalation_policies,update_escalation_policy,list_escalation_paths,update_escalation_path,list_escalation_levels" ``` ### 📊 Monitoring & Alerting (40 tools) *For platform teams setting up observability* ```bash ROOTLY_MCP_ENABLED_TOOLS="list_alerts,get_alert,get_alert_by_short_id,create_alert_group,update_alert_group,list_alert_groups,create_alert_routing_rule,update_alert_routing_rule,list_alert_routing_rules,list_alert_events,get_alert_event,update_alert_event,create_heartbeat,update_heartbeat,list_heartbeats,get_heartbeat,create_pulse,update_pulse,list_pulses,get_pulse,create_dashboard,update_dashboard,list_dashboards,get_dashboard,create_dashboard_panel,update_dashboard_panel,list_status_pages,get_status_page,update_status_page,list_status_page_templates,get_status_page_template,list_communications_templates,update_communications_template,create_live_call_router,update_live_call_router,list_services,list_teams,get_current_user,list_environments,list_severities,list_endpoints" ``` ### 📋 Post-Incident Analysis (30 tools) *For SREs doing retrospectives and process improvement* ```bash ROOTLY_MCP_ENABLED_TOOLS="get_incident,update_incident,find_related_incidents,suggest_solutions,list_incident_action_items,create_incident_action_item,update_incident_form_field_selection,create_post_incident_review,update_post_incident_review,list_post_incident_reviews,get_post_incident_review,create_retrospective_step,update_retrospective_step,list_retrospective_steps,create_retrospective_process,update_retrospective_process,list_retrospective_processes,create_playbook,update_playbook,list_playbooks,get_playbook,create_playbook_task,update_playbook_task,list_causes,get_cause,update_cause,list_incident_types,get_incident_type,update_incident_type,get_current_user" ``` ### 📈 Analytics & Reporting (15 tools) *For leadership and metrics teams (read-only focus)* ```bash ROOTLY_MCP_ENABLED_TOOLS="list_incidents,search_incidents,collect_incidents,list_teams,list_services,list_schedules,get_oncall_shift_metrics,get_shift_incidents,list_dashboards,get_dashboard,list_alerts,list_heartbeats,list_pulses,get_current_user,list_endpoints" ``` ### Multiple MCP Instances for Different Teams You can run multiple MCP instances with different tool subsets: ```json { "mcpServers": { "rootly-incident-response": { "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"], "env": { "ROOTLY_API_TOKEN": "", "ROOTLY_MCP_ENABLED_TOOLS": "list_incidents,get_incident,create_incident,find_related_incidents,suggest_solutions..." } }, "rootly-oncall-management": { "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"], "env": { "ROOTLY_API_TOKEN": "", "ROOTLY_MCP_ENABLED_TOOLS": "list_schedules,update_schedule,create_override_shift,get_oncall_shift_metrics..." } } } } ``` ### 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**: Uses bounded pagination and compact incident responses 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 incidents, teams, on-call status, and workflow guides as structured resources for AI context - **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 tool surface depends on deployment profile: - Hosted default: about **218 tools** - Hosted slim profile: about **70 tools** - Self-hosted default: about **218 tools** ### Custom Agentic Tools - `check_oncall_health_risk` - `check_responder_availability` - `collect_incidents` - `create_incident` - create a new incident with a scoped set of fields for agent workflows - `create_override_recommendation` - `find_related_incidents` - `get_incident` - retrieve a single incident for direct verification, including PIR-related fields - `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_incidents` - `list_shifts` - `search_incidents` - `suggest_solutions` - `update_incident` - scoped incident update tool for `summary` and `retrospective_progress_status` ### OpenAPI-Generated Tools > **Tool naming:** all tools use `snake_case`. The historical `camelCase` names > (e.g. `getScheduleShifts`, `listIncidents`) are no longer advertised in > `tools/list`, but remain callable as hidden aliases — they are transparently > routed to their `snake_case` canonical. Update configs and `ROOTLY_MCP_ENABLED_TOOLS` > allowlists to the `snake_case` names; legacy camelCase allowlist entries are > auto-canonicalized. ```text list_workflow_runs create_incident_action_item create_incident_form_field_selection create_workflow_task get_alert get_alert_event get_alert_group get_alert_routing_rule get_alert_source get_alert_urgency get_catalog get_catalog_entity get_cause get_current_user get_custom_form get_environment get_escalation_level get_escalation_path get_escalation_policy get_form_field get_form_field_ … ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [rootlyhq](https://github.com/rootlyhq) - **Source:** [rootlyhq/rootly-mcp-server](https://github.com/rootlyhq/rootly-mcp-server) - **License:** Apache-2.0 - **Homepage:** https://rootly.com/ai-labs Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v2.2.4 — what this tool can access: - **Network access:** yes - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **2.2.4** — security scan: flagged — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-rootly-ai-labs-rootly-mcp-server - Seller: https://agentstack.voostack.com/s/rootlyhq - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.