incident.io with LlamaIndex

How to integrate incident.io MCP with LlamaIndex

Introduction TL;DR What is LlamaIndex What is the incident.io MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Tool Router Step-by-step Guide Complete Code Conclusion How to build incident.io MCP Agent with another framework Explore Other Toolkits FAQ

Connect incident.io without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting incident.io to LlamaIndex 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 LlamaIndex 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:

Set your OpenAI and Composio API keys
Install LlamaIndex and Composio packages
Create a Composio Tool Router session for incident.io
Connect LlamaIndex to the incident.io MCP server
Build a incident.io-powered agent using LlamaIndex
Interact with incident.io through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

ReAct Agent: Reasoning and acting pattern for tool-using agents
MCP Tools: Native support for Model Context Protocol
Context Management: Maintain conversation context across interactions
Async Support: Built for async/await patterns

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:

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

Step-by-step Guide

Prerequisites

Before you begin, make sure you have:

Python 3.8/Node 16 or higher installed
A Composio account with the API key
An OpenAI API key
A incident.io account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and incident.io

OpenAI API key (OPENAI_API_KEY)

Go to the OpenAI dashboard
Create an API key if you don't have one
Assign it to OPENAI_API_KEY in .env

Composio API key and user ID

Log into the Composio dashboard
Copy your API key from Settings
- Use this as COMPOSIO_API_KEY
Pick a stable user identifier (email or ID)
- Use this as COMPOSIO_USER_ID

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

composio-llamaindex: Composio's LlamaIndex integration
llama-index: Core LlamaIndex framework
llama-index-llms-openai: OpenAI LLM integration
llama-index-tools-mcp: MCP client for LlamaIndex
python-dotenv: Environment variable management

Set environment variables

bash

OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

Authenticate with OpenAI's GPT-5 model
Connect to Composio's Tool Router
Identify your Composio user session for incident.io access

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

Create a new file called incident.io_llamaindex_agent.py and import the required modules:

Key imports:

asyncio: For async/await support
Composio: Main client for Composio services
LlamaIndexProvider: Adapts Composio tools for LlamaIndex
ReActAgent: LlamaIndex's reasoning and action agent
BasicMCPClient: Connects to MCP endpoints
McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set in the environment")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment")

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["incident_io"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform incident.io actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform incident.io actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

What's happening here:

We create a Composio client using your API key and configure it with the LlamaIndex provider
We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, incident.io)
The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
LlamaIndex will connect to this endpoint to dynamically discover and use the available incident.io tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

We're creating a direct terminal interface to chat with your incident.io database
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

What's happening here:

We're orchestrating the entire application flow
The agent gets built with proper error handling
Then we kick off the interactive chat loop so you can start talking to incident.io

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with incident.io, then start asking questions.

Complete Code

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

import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["incident_io"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform incident.io actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform incident.io actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

Conclusion

You've successfully connected incident.io to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes incident.io tools through an MCP endpoint
LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
The agent becomes more capable without increasing prompt size
Async Python provides clean, efficient execution of agent workflows

You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

How to build incident.io MCP Agent with another framework

OpenAI Agents SDK

Use incident.io MCP with OpenAI Agents SDK

Claude Agent SDK

Use incident.io MCP with Claude Agent SDK

Google ADK

Use incident.io MCP with Google ADK

LangChain

Use incident.io MCP with LangChain

Vercel AI SDK

Use incident.io MCP with Vercel AI SDK

Mastra AI

Use incident.io MCP with Mastra AI

CrewAI

Use incident.io MCP with CrewAI

Claude Code

Use incident.io MCP with Claude Code

Codex

Use incident.io MCP with Codex

Explore Other Toolkits

Addressfinder

Api Key

Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.

Agiled

API Key

Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.

Airtable

OAuth2Bearer TokenAPI Key

Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.

TOOLKIT MARKETPLACE

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 LlamaIndex?

Yes, you can. LlamaIndex 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

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

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate incident.io MCP with LlamaIndex

Table of Contents

Connect incident.io without Auth hassles

Introduction

TL;DR

What is LlamaIndex?

What is the incident.io MCP server, and what's possible with it?

Supported Tools & Triggers

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

What is Tool Router?

How the Tool Router works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI, Composio, and incident.io

Installing dependencies

Set environment variables

Import modules

Load environment variables and initialize Composio

Create a Tool Router session and build the agent function

Create an interactive chat loop

Define the main entry point

Run the agent

Complete Code

Conclusion

How to build incident.io MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Google ADK

LangChain

Vercel AI SDK

Mastra AI

CrewAI

Claude Code

Codex

Explore Other Toolkits

Addressfinder

Agiled

Airtable

FAQ

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

Can I use Tool Router MCP with LlamaIndex?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability