How to Connect Rootly to Claude via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Rootly, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Rootly + Claude

Rootly incident management from any AI agent: declare, update, mitigate and resolve incidents with timeline notes and action items, acknowledge and resolve alerts, see who is on call, publish status page updates and read retrospectives, services, teams and severities.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

ROOTLY_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Rootly account.

1. In Rootly open the organization menu, then Organization Settings, API Keys, and create a key. A Global key sees the whole organization, a Team key only that team's records, a Personal key acts with your own permissions.
2. Give the key a role that can read what you need, plus write permission for incidents, alerts and action items if the AI should change them.
3. Paste only the key, without Bearer in front, into ROOTLY_API_KEY and run rootly_get_current_user. It shows the user the key acts as; a Global or Team key answers with the user who created it.

What is going on: rootly_list_incidents with status: "started,mitigated" (or in_triage) lists the current incidents; filters cover severity, service, team, environment, type, free text and dates. rootly_get_incident shows one incident with all its attributes, rootly_list_incident_events its timeline and rootly_list_incident_action_items its tasks. To find ids the AI uses rootly_list_severities, rootly_list_services, rootly_get_service, rootly_list_functionalities, rootly_get_functionality, rootly_list_teams, rootly_get_team, rootly_list_environments, rootly_list_incident_types and rootly_list_users.

Running an incident: rootly_create_incident declares one. With an idempotency_key a retry within 24 hours returns the same incident instead of a second one; kind test is for a try. rootly_update_incident changes title, summary, severity, services, teams, labels or status; a list replaces the whole list. rootly_add_incident_event adds internal or external timeline notes, rootly_mitigate_incident and rootly_resolve_incident move the incident on with a short note. Action items: rootly_list_action_items across all incidents, rootly_get_action_item, rootly_create_action_item and rootly_update_action_item (for example status done).

Alerts: rootly_list_alerts (for example status triggered or open), rootly_get_alert with the raw payload the source sent, rootly_acknowledge_alert (the escalation stops paging the next level) and rootly_resolve_alert, which can also resolve the incidents the alert is attached to.

On-call: rootly_list_oncalls answers who is on call now or in a time window. rootly_list_schedules, rootly_get_schedule, rootly_get_schedule_shifts, rootly_list_shifts and rootly_list_escalation_policies give the details.

Status pages and retrospectives: rootly_list_status_pages, rootly_get_status_page and rootly_list_incident_status_page_events read; rootly_create_status_page_event publishes an update (investigating, identified, monitoring, resolved). rootly_list_retrospectives and rootly_get_retrospective read the post-mortems.

Before writing: a normal incident runs workflows, opens a Slack channel and can page people; a status page update is public and can e-mail the subscribers. So the AI shows you what it is about to do and waits for your yes. A private incident cannot be made public again.

Switched off at install: no tool. Everything is on from the start; what the AI may do is limited by the role and team of the key.

Data formats: answers follow JSON:API: records are in data (id, type, attributes, relationships), records embedded with include in included. Ids are UUIDs, user ids are numbers. The human incident number is attributes.sequential_id (INC-123). Times are ISO 8601, in UTC unless a time zone is given. rootly_list_incidents and rootly_list_alerts return a compact set of attributes by default; fields: "" returns all of them. Zoom meeting passwords and host links are left out of incident answers.

Paging: lists return meta with current_page, next_page (null on the last page), total_count and total_pages; the AI calls again with page_number. Incidents and alerts also accept the cursor page_after from meta.next_cursor. page_size goes up to 100, but small pages work better because Rootly records are large.

Common errors: 401 means a wrong or revoked key, 403 a key whose role or team does not allow the call, 404 an unknown id or one outside the key's team, 422 a validation error whose errors name the field, 429 the rate limit (the X-RateLimit-* headers say when it resets; wait and retry).

The connector does not delete incidents, alerts or action items, does not change schedules, escalation policies or status pages and does not write retrospectives.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Claude

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Recommended path: works on claude.ai web without editing any config file.

1. In Claude, open Customize → Connectors.
2. Click +, then Add custom connector.
3. Enter a name, e.g. Rootly, and the remote MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add.
4. Click Connect and sign in to AnythingMCP (OAuth) to allow access.

All tools below appear in your chat: start typing prompts.

Available tools

Example prompts

• "Which incidents are open right now, and who is on call for the payments service?"
• "Show me the timeline of INC-482 and list its open action items."
• "Declare a SEV2 incident for slow checkout on the checkout service. Show me the details before you create it."
• "Acknowledge the triggered Datadog alerts for the API gateway and tell me what they say."
• "Post a Monitoring update for INC-482 on our status page: the fix is deployed and we are watching the error rate."

FAQ

Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.

Next steps

• Connector landing page
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse
• Connect to Microsoft Copilot