How to connect incident.io to Claude

Connect Claude Web, Desktop and Cowork to incident.io MCP. Create a new incident for database outage, list all active incidents from this week, and more using natural language, with authentication handled for you.

incident.io logoincident.io
Api Key

incident.io is an incident management and response platform for modern teams. It helps streamline incident reporting, collaboration, and resolution.

112 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 incident.io account to Claude via Composio Connect, enabling it to create a new incident for database outage, list all active incidents from this week, assign on-call responder to latest 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 incident.io with

Connecting incident.io 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 incident.io account

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

For example, ask Claude to:

  • "Create a new incident for database outage"
  • "List all active incidents from this week"
  • "Assign on-call responder to latest incident"

It will prompt you to authenticate and authorize access.

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

What is the incident.io Claude Connector, and what's possible with it?

The incident.io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your incident.io account. It provides structured and secure access so your agent can perform incident.io operations on your behalf.

Troubleshooting

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

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

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

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

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

  • 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 incident.io.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the incident.io authorization link not work?

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

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

4. Why do incident.io actions fail after they worked before?

The incident.io connection can expire or lose permission.

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

5. How do I switch to a different incident.io account?

Claude can manage the incident.io connection for you.

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

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

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

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If incident.io 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 incident.io.
TOOLS

Supported Tools

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

Create Alert Attribute V2

Tool to create an alert attribute in incident.

Create Alert Route V2

Tool to create an alert route in incident.

Create Alert Source V2

Tool to create a new alert source in incident.

Create Catalog Entry V2

Tool to create a catalog entry in incident.

Create Catalog Entry V3

Tool to create a catalog entry in incident.

Create Catalog Type V3

Tool to create a new catalog type in incident.

Create Custom Field Option

Tool to create a new custom field option in incident.

Create Custom Field V2

Tool to create a custom field in incident.

Create Escalation V2

Tool to create an escalation in incident.

Create Incident Role

Tool to create a new incident role in incident.

Create Incident Role V2

Tool to create a new incident role in incident.

Create Incident Status

Tool to create a new incident status in incident.

Create Incident V1

Tool to create a new incident in incident.

Create Incident V2

Tool to create a new incident in incident.

Create Managed Resource V2

Tool to create a managed resource in incident.

Create Severity

Tool to create a new severity level in incident.

Delete Alert Attribute V2

Tool to delete an alert attribute from incident.

Delete Alert Route V2

Tool to delete an alert route from incident.

Delete Alert Source V2

Tool to delete an alert source from incident.

Delete Catalog Entry V2

Tool to delete a catalog entry from incident.

Delete Catalog Entry V3

Tool to archive a catalog entry from incident.

Delete Catalog Type V2

Tool to delete a catalog type from incident.

Delete Catalog Type V3

Tool to archive a catalog type and all its entries from incident.

Delete Custom Field

Tool to delete a custom field from incident.

Delete Custom Field Option

Tool to delete a custom field option in incident.

Delete Custom Field V2

Tool to delete a custom field from incident.

Delete Escalation Path V2

Tool to delete an escalation path from incident.

Delete Incident Role V2

Tool to delete an incident role by ID.

Delete Incident Role V1

Tool to delete an incident role by ID.

Delete Incident Status V1

Tool to delete an incident status by its ID.

Delete Schedule V2

Tool to delete a schedule from incident.

Delete Severity

Tool to delete a severity in incident.

Delete Workflow V2

Tool to delete a workflow from incident.

Edit Incident V2

Tool to edit an existing incident in incident.

Show Alert Attribute V2

Tool to retrieve a specific alert attribute by its ID from incident.

Show Alert Routes V2

Tool to retrieve a specific alert route configuration by its ID from incident.

Show Alert Source V2

Tool to retrieve a specific alert source by its ID from incident.

Show Entry Catalog V2

Tool to retrieve a specific catalog entry by ID from incident.

Get Catalog Entry V3

Tool to retrieve a specific catalog entry by ID from incident.

Get Catalog Type V2

Tool to retrieve a specific catalog type by ID from incident.

Get Catalog Type V3

Tool to retrieve a specific catalog type by ID from incident.

Get Custom Field Option

Tool to retrieve a specific custom field option by its ID.

Get Custom Field V1

Tool to retrieve details of a specific custom field by ID in incident.

Get Custom Field V2

Tool to retrieve details of a specific custom field by ID using the V2 API in incident.

Show Escalations V2

Tool to retrieve a specific escalation by ID from incident.

Get Incident Role

Tool to retrieve a specific incident role by ID.

Get Incident Role V2

Tool to retrieve a specific incident role by ID using V2 API.

Get Incident Status

Tool to retrieve details of a specific incident status by ID.

Get Incident Timestamp V2

Tool to retrieve a specific incident timestamp by ID using V2 API.

Get Incident Type

Tool to retrieve detailed information about a specific incident type by ID.

Get Incident by ID (V1)

Tool to retrieve a specific incident by ID.

Get Incident by ID (V2)

Tool to retrieve a specific incident by ID using V2 API.

Show Schedules V2

Tool to retrieve a specific schedule by ID from incident.

Get Severity V1

Tool to retrieve a specific severity by ID from incident.

Get User V2

Tool to retrieve a specific user by ID from incident.

Get Workflow V2

Tool to retrieve a specific workflow by ID from incident.

List Actions V1

Tool to list actions from incidents.

List Actions V2

Tool to retrieve a list of actions from incident.

List Alert Attributes V2

Tool to list all available alert attributes.

List Alert Routes V2

Tool to list alert routes from incident.

List Alert Sources V2

Tool to list all configured alert sources in incident.

List Alerts V2

Tool to list alerts from incident.

List Catalog Entries V2

Tool to list entries from a catalog type in incident.

List Catalog Entries V3

Tool to list entries from a catalog type in incident.

List Catalog Resources V2

Tool to retrieve all available catalog resource types.

List Catalog Resources V3

Tool to retrieve all available catalog resource types from the V3 API.

List Catalog Types V2

Tool to retrieve all catalog types configured for an organization.

List Catalog Types V3

Tool to retrieve all catalog types configured for an organization using V3 API.

List Custom Field Options V1

Tool to list all options for a specific custom field in incident.

List Custom Fields V1

Tool to list all custom fields for an organization.

List Custom Fields V2

Tool to list all custom fields V2 for an organization.

List Escalation Paths V2

Tool to list escalation paths from incident.

List Escalations V2

Tool to list escalations from incident.

List Follow-ups V2

Tool to retrieve a list of follow-ups from incident.

Get API Key Identity

Tool to retrieve identity information for the current API key.

List Incident Alerts V2

Tool to list incident alerts from incident.

List Incident Attachments V1

Tool to list incident attachments from incident.

List Incident Relationships V1

Tool to list incident relationships for a given incident.

List Incident Roles V1

Tool to list all incident roles for an organization.

List Incident Roles V2

Tool to list all incident roles for an organization using V2 API.

List Incident Statuses V1

Tool to list all incident statuses configured for an organization.

List Incidents V1

Tool to list incidents from incident.

List Incidents V2

Tool to list incidents from incident.

List Incident Timestamps V2

Tool to list all incident timestamp configurations using V2 API.

List Incident Types V1

Tool to list all incident types for an organization.

List Incident Updates V2

Tool to list incident updates from incident.

List IP allowlists

Tool to retrieve the current IP allowlist configuration for incident.

List Schedule Entries V2

Tool to list schedule entries for a specific schedule in incident.

List Schedules V2

Tool to list schedules from incident.

List Severities V1

Tool to retrieve all incident severities configured for an organization.

List Status Pages V2

Tool to list status pages from incident.

List Users V2

Tool to list users in incident.

List Workflows V2

Tool to list workflows from incident.

Update Alert Attribute V2

Tool to update an alert attribute in incident.

Update Alert Source V2

Tool to update an existing alert source configuration in incident.

Bulk Update Catalog Entries V3

Tool to bulk update catalog entries in incident.

Update Catalog Entry V2

Tool to update an existing catalog entry in incident.

Update Catalog Entry V3

Tool to update an existing catalog entry in incident.

Update Catalog Type V2

Tool to update a catalog type in incident.

Update Catalog Type V3

Tool to update a catalog type in incident.

Update Custom Field Option V1

Tool to update a custom field option in incident.

Update Custom Fields V1

Tool to update an existing custom field configuration in incident.

Update Custom Field V2

Tool to update an existing custom field in incident.

Update Escalation Path V2

Tool to update an escalation path in incident.

Update Incident Role

Tool to update an existing incident role in incident.

Update Incident Role V2

Tool to update an existing incident role in incident.

Update Incident Status

Tool to update an existing incident status in incident.

Update Schedule V2

Tool to update an existing schedule in incident.

Update Catalog Type Schema V2

Tool to update the schema of a catalog type in incident.

Update Catalog Type Schema V3

Tool to update the schema of a catalog type in incident.

Update Severity

Tool to update a severity in incident.

Update Workflow V2

Tool to update an existing workflow in incident.

FAQ

Frequently asked questions

With a standalone incident.io MCP server, the agents and LLMs can only access a fixed set of incident.io tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from incident.io 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 incident.io tools.

Yes, absolutely. You can configure which incident.io 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 incident.io data and credentials are handled as safely as possible.

Start with incident.io.It takes 30 seconds.

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

Start building