How to integrate incident.io MCP with LlamaIndex

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.

Get started for free Get a demo

incident.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

Managed auth

Connect incident.io without auth hassles

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

Try for free

Introduction

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.

Also integrate incident.io with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI CrewAI

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.

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:

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

Step by step10 STEPS

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

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

@composio/llamaindex: Composio's LlamaIndex integration
@llamaindex/openai: OpenAI LLM integration
@llamaindex/tools: MCP client for LlamaIndex
@llamaindex/workflow: Workflow framework for LlamaIndex
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 "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

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

Key imports:

dotenv.config loads .env at runtime
readline gives us a simple CLI chat loop
Composio is the main Composio SDK client
mcp connects to an MCP endpoint
createAgent builds a LlamaIndex agent
openai configures the LLM backend

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

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 function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["incident_io"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform incident.io actions." ,
    llm,
    tools,
  });

  return agent;
}

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 function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

We're creating a direct terminal interface to chat with incident.io
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
The agent processes the request, selects appropriate incident.io tools, and returns a result
We extract the answer from the result data structure and display it to the user
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are streamed in a clear, readable format

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

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 "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["incident_io"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform incident.io actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

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.

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

Use incident.io MCP with OpenAI Agents SDK

Claude Agent SDK

Use incident.io MCP with Claude Agent SDK

Claude Code

Use incident.io MCP with Claude Code

Claude Cowork

Use incident.io MCP with Claude Cowork

Codex

Use incident.io MCP with Codex

OpenClaw

Use incident.io MCP with OpenClaw

Hermes

Use incident.io MCP with Hermes

CLI

Use incident.io MCP with CLI

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

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Sheets

Oauth2

Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.

Notion

Oauth2Api Key

Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

Airtable

Oauth2Api 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.

Asana

Oauth2

Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.

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. 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.

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 FREE BOOK A DEMO

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

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

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

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

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

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

Co-Founder, Ingram Technologies