How to connect Rootly to Claude

Connect Claude Web, Desktop and Cowork to Rootly MCP. List all open incident action items, get details for action item id 12345, and more using natural language, with authentication handled for you.

Rootly logoRootly
Api Key

Rootly is an AI-powered incident management platform for automating response workflows and collaboration. It helps teams streamline incident handling, reduce downtime, and integrate with tools like Slack and PagerDuty.

6 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Rootly account to Claude via Composio Connect, enabling it to list all open incident action items, get details for action item ID 12345, delete completed action item from incident, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Rootly with

Connecting Rootly to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Rootly account

Back in Claude, ask it to connect to Rootly or give it any Rootly-related task.

For example, ask Claude to:

  • "List all open incident action items"
  • "Get details for action item ID 12345"
  • "Delete completed action item from incident"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Rootly account is ready to use.

What is the Rootly Claude Connector, and what's possible with it?

The Rootly MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Rootly account. It provides structured and secure access to your incident action items, so your agent can list, review, retrieve detailed information, and manage follow-up tasks on your behalf during or after incidents.

  • Comprehensive action item retrieval: Instantly list all incident-related action items, making it easy for your agent to track ongoing or outstanding tasks.
  • Detailed action item inspection: Pull up in-depth information for any action item—including summary, description, priority, status, and due date—to keep teams informed and accountable.
  • Streamlined task management: Direct your agent to remove obsolete or completed action items, ensuring your incident follow-up list stays relevant and up to date.
  • Automated follow-up coordination: Use your agent to monitor and organize post-incident tasks, helping your team close the loop on every incident and maintain operational excellence.

Troubleshooting

1. Why does Claude not use the Composio connector for Rootly?

The connector can show as connected, but Claude must use it in each Rootly conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Rootly again.

2. Why does Claude show an MCP server error before Rootly connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Rootly.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Rootly.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Rootly authorization link not work?

The Composio connector is one server. Your Rootly account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Rootly connection.
  • Composio creates a fresh Rootly authorization link.
  • Open that link in your browser and finish the Rootly sign-in.

4. Why do Rootly actions fail after they worked before?

The Rootly connection can expire or lose permission.

  • Ask Claude to inspect the Rootly connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Rootly account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Rootly.
  • If the action still fails with a permission error, check that the connected account has that permission in Rootly itself.

5. How do I switch to a different Rootly account?

Claude can manage the Rootly connection for you.

  • Ask Claude to disconnect or delete the current Rootly account.
  • Ask Claude to connect Rootly again.
  • Open the new Composio authorization link for Rootly.
  • Sign in with the other Rootly account in the browser.
  • After the account connects, ask Claude to retry the Rootly task.

6. Why is my Rootly connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Rootly connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Rootly tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Rootly.
TOOLS

Supported Tools

Every Rootly action and event your agent gets out of the box.

Delete Action Item

This tool allows for the deletion of a specific action item in Rootly.

Delete Incident

Tool to delete an incident in Rootly by ID.

Get Action Item Details

Retrieves detailed information about a specific action item by its ID from Rootly.

Get Incident Details

Tool to retrieve full details for a single Rootly incident by ID.

List Action Items

This tool retrieves a list of all action items for an organization in Rootly.

Update Incident

Tool to update fields on an existing Rootly incident by ID.

FAQ

Frequently asked questions

With a standalone Rootly MCP server, the agents and LLMs can only access a fixed set of Rootly tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Rootly and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Rootly tools.

Yes, absolutely. You can configure which Rootly scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Rootly data and credentials are handled as safely as possible.

Start with Rootly.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Rootly tool your agent needs.Free to start.

Start building