Rootly MCP Server

An MCP server for the Rootly API for Cursor, Windsurf, Claude, and other MCP clients. Exposed over MCP by the rootly mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• 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

Its toolset

Everything the assistant can do here goes through one of these:

• Self — hosted default: about 218 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
• Prerequisites — The Prerequisites tool exposed by this server

Configuration

You will need 8 environment variables: ROOTLY_API_TOKEN, ROOTLY_MCP_ENABLE_WRITE_TOOLS, ROOTLY_MCP_ENABLED_TOOLS, ONCALLHEALTH_API_KEY, YOUR_ROOTLY_API_TOKEN, ROOTLY_MCPCAT_PROJECT_ID, SENTRY_DSN, ROOTLY_OPENAI_APPS_CHALLENGE_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.12 or higher - uv package manager - Rootly API token

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Rootly's toolset — Self, check_oncall_health_risk, collect_incidents and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Rootly-AI-Labs; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Rootly's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Rootly.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the rootly mcp server does with a few real requests.