How to integrate incident.io MCP with Google ADK

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

Get started for freeGet a demo
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

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

Also integrate incident.io with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLILangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get a incident.io account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for incident.io
  • Build an agent that connects to incident.io through MCP
  • Interact with incident.io using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK 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

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to incident.io via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

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

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with incident.io operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

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

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

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

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with incident.io operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated incident.io with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with incident.io using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate incident.io tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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.

FRAMEWORKS

How to build incident.io MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use incident.io MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use incident.io MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use incident.io MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use incident.io MCP with Claude Cowork

Codex logo

Codex

Use incident.io MCP with Codex

OpenClaw logo

OpenClaw

Use incident.io MCP with OpenClaw

Hermes logo

Hermes

Use incident.io MCP with Hermes

CLI logo

CLI

Use incident.io MCP with CLI

LangChain logo

LangChain

Use incident.io MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use incident.io MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use incident.io MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use incident.io MCP with LlamaIndex

CrewAI logo

CrewAI

Use incident.io MCP with CrewAI

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. Google ADK 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
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

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

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

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's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

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

Nirman Dave
Nirman Dave
CEO, Zams

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

Ryan Yu
Ryan Yu
Founder, Extra Thursday

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

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

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.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies