How to integrate incident.io MCP with Claude Agent SDK

GET STARTED FOR FREE
Framework Integration Gradient
incident.io Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting incident.io to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working incident.io agent that can create a new incident for database outage, list all active incidents from this week, assign on-call responder to latest incident through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a incident.io account through Composio's incident.io MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for incident.io
  • Configure an AI agent that can use incident.io as a tool
  • Run a live chat session where you can ask the agent to perform incident.io operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the incident.io MCP server, 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.

Supported Tools & Triggers

Tools
Create Alert Attribute V2Tool to create an alert attribute in incident.
Create Alert Route V2Tool to create an alert route in incident.
Create Alert Source V2Tool to create a new alert source in incident.
Create Catalog Entry V2Tool to create a catalog entry in incident.
Create Catalog Entry V3Tool to create a catalog entry in incident.
Create Catalog Type V3Tool to create a new catalog type in incident.
Create Custom Field OptionTool to create a new custom field option in incident.
Create Custom Field V2Tool to create a custom field in incident.
Create Escalation V2Tool to create an escalation in incident.
Create Incident RoleTool to create a new incident role in incident.
Create Incident Role V2Tool to create a new incident role in incident.
Create Incident StatusTool to create a new incident status in incident.
Create Incident V1Tool to create a new incident in incident.
Create Incident V2Tool to create a new incident in incident.
Create Managed Resource V2Tool to create a managed resource in incident.
Create SeverityTool to create a new severity level in incident.
Delete Alert Attribute V2Tool to delete an alert attribute from incident.
Delete Alert Route V2Tool to delete an alert route from incident.
Delete Alert Source V2Tool to delete an alert source from incident.
Delete Catalog Entry V2Tool to delete a catalog entry from incident.
Delete Catalog Entry V3Tool to archive a catalog entry from incident.
Delete Catalog Type V2Tool to delete a catalog type from incident.
Delete Catalog Type V3Tool to archive a catalog type and all its entries from incident.
Delete Custom FieldTool to delete a custom field from incident.
Delete Custom Field OptionTool to delete a custom field option in incident.
Delete Custom Field V2Tool to delete a custom field from incident.
Delete Escalation Path V2Tool to delete an escalation path from incident.
Delete Incident Role V2Tool to delete an incident role by ID.
Delete Incident Role V1Tool to delete an incident role by ID.
Delete Incident Status V1Tool to delete an incident status by its ID.
Delete Schedule V2Tool to delete a schedule from incident.
Delete SeverityTool to delete a severity in incident.
Delete Workflow V2Tool to delete a workflow from incident.
Edit Incident V2Tool to edit an existing incident in incident.
Show Alert Attribute V2Tool to retrieve a specific alert attribute by its ID from incident.
Show Alert Routes V2Tool to retrieve a specific alert route configuration by its ID from incident.
Show Alert Source V2Tool to retrieve a specific alert source by its ID from incident.
Show Entry Catalog V2Tool to retrieve a specific catalog entry by ID from incident.
Get Catalog Entry V3Tool to retrieve a specific catalog entry by ID from incident.
Get Catalog Type V2Tool to retrieve a specific catalog type by ID from incident.
Get Catalog Type V3Tool to retrieve a specific catalog type by ID from incident.
Get Custom Field OptionTool to retrieve a specific custom field option by its ID.
Get Custom Field V1Tool to retrieve details of a specific custom field by ID in incident.
Get Custom Field V2Tool to retrieve details of a specific custom field by ID using the V2 API in incident.
Show Escalations V2Tool to retrieve a specific escalation by ID from incident.
Get Incident RoleTool to retrieve a specific incident role by ID.
Get Incident Role V2Tool to retrieve a specific incident role by ID using V2 API.
Get Incident StatusTool to retrieve details of a specific incident status by ID.
Get Incident Timestamp V2Tool to retrieve a specific incident timestamp by ID using V2 API.
Get Incident TypeTool 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 V2Tool to retrieve a specific schedule by ID from incident.
Get Severity V1Tool to retrieve a specific severity by ID from incident.
Get User V2Tool to retrieve a specific user by ID from incident.
Get Workflow V2Tool to retrieve a specific workflow by ID from incident.
List Actions V1Tool to list actions from incidents.
List Actions V2Tool to retrieve a list of actions from incident.
List Alert Attributes V2Tool to list all available alert attributes.
List Alert Routes V2Tool to list alert routes from incident.
List Alert Sources V2Tool to list all configured alert sources in incident.
List Alerts V2Tool to list alerts from incident.
List Catalog Entries V2Tool to list entries from a catalog type in incident.
List Catalog Entries V3Tool to list entries from a catalog type in incident.
List Catalog Resources V2Tool to retrieve all available catalog resource types.
List Catalog Resources V3Tool to retrieve all available catalog resource types from the V3 API.
List Catalog Types V2Tool to retrieve all catalog types configured for an organization.
List Catalog Types V3Tool to retrieve all catalog types configured for an organization using V3 API.
List Custom Field Options V1Tool to list all options for a specific custom field in incident.
List Custom Fields V1Tool to list all custom fields for an organization.
List Custom Fields V2Tool to list all custom fields V2 for an organization.
List Escalation Paths V2Tool to list escalation paths from incident.
List Escalations V2Tool to list escalations from incident.
List Follow-ups V2Tool to retrieve a list of follow-ups from incident.
Get API Key IdentityTool to retrieve identity information for the current API key.
List Incident Alerts V2Tool to list incident alerts from incident.
List Incident Attachments V1Tool to list incident attachments from incident.
List Incident Relationships V1Tool to list incident relationships for a given incident.
List Incident Roles V1Tool to list all incident roles for an organization.
List Incident Roles V2Tool to list all incident roles for an organization using V2 API.
List Incident Statuses V1Tool to list all incident statuses configured for an organization.
List Incidents V1Tool to list incidents from incident.
List Incidents V2Tool to list incidents from incident.
List Incident Timestamps V2Tool to list all incident timestamp configurations using V2 API.
List Incident Types V1Tool to list all incident types for an organization.
List Incident Updates V2Tool to list incident updates from incident.
List IP allowlistsTool to retrieve the current IP allowlist configuration for incident.
List Schedule Entries V2Tool to list schedule entries for a specific schedule in incident.
List Schedules V2Tool to list schedules from incident.
List Severities V1Tool to retrieve all incident severities configured for an organization.
List Status Pages V2Tool to list status pages from incident.
List Users V2Tool to list users in incident.
List Workflows V2Tool to list workflows from incident.
Update Alert Attribute V2Tool to update an alert attribute in incident.
Update Alert Source V2Tool to update an existing alert source configuration in incident.
Bulk Update Catalog Entries V3Tool to bulk update catalog entries in incident.
Update Catalog Entry V2Tool to update an existing catalog entry in incident.
Update Catalog Entry V3Tool to update an existing catalog entry in incident.
Update Catalog Type V2Tool to update a catalog type in incident.
Update Catalog Type V3Tool to update a catalog type in incident.
Update Custom Field Option V1Tool to update a custom field option in incident.
Update Custom Fields V1Tool to update an existing custom field configuration in incident.
Update Custom Field V2Tool to update an existing custom field in incident.
Update Escalation Path V2Tool to update an escalation path in incident.
Update Incident RoleTool to update an existing incident role in incident.
Update Incident Role V2Tool to update an existing incident role in incident.
Update Incident StatusTool to update an existing incident status in incident.
Update Schedule V2Tool to update an existing schedule in incident.
Update Catalog Type Schema V2Tool to update the schema of a catalog type in incident.
Update Catalog Type Schema V3Tool to update the schema of a catalog type in incident.
Update SeverityTool to update a severity in incident.
Update Workflow V2Tool to update an existing workflow in incident.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A incident.io account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with incident.io functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for incident.io
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["incident_io"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for incident.io
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to incident.io tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to incident.io
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with incident.io and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for incident.io
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["incident_io"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to incident.io tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with incident.io through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build incident.io MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use incident.io MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use incident.io MCP with Google ADK

LangChain

LangChain

Use incident.io MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use incident.io MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use incident.io MCP with Mastra AI

LlamaIndex

LlamaIndex

Use incident.io MCP with LlamaIndex

CrewAI

CrewAI

Use incident.io MCP with CrewAI

Claude Code

Claude Code

Use incident.io MCP with Claude Code

Codex

Codex

Use incident.io MCP with Codex

FAQ

What are the differences in Tool Router MCP and incident.io MCP?

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.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK 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.

Can I manage the permissions and scopes for incident.io while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free