How to integrate Ashby MCP with Vercel AI SDK v6

This guide walks you through connecting Ashby to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Ashby agent that can list all candidates for open roles, post a new job opening for engineering, summarize candidates in interview stage through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Ashby account through Composio's Ashby 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
Ashby logoAshby
Api Key

Ashby is an applicant tracking system that handles job postings, candidate management, and hiring analytics.

125 Tools

Introduction

This guide walks you through connecting Ashby to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Ashby agent that can list all candidates for open roles, post a new job opening for engineering, summarize candidates in interview stage through natural language commands.

This guide will help you understand how to give your Vercel AI SDK agent real control over a Ashby account through Composio's Ashby MCP server.

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

Also integrate Ashby with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • How to set up and configure a Vercel AI SDK agent with Ashby integration
  • Using Composio's Tool Router to dynamically load and access Ashby tools
  • Creating an MCP client connection using HTTP transport
  • Building an interactive CLI chat interface with conversation history management
  • Handling tool calls and results within the Vercel AI SDK framework

What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.

Key features include:

  • streamText: Core function for streaming responses with real-time tool support
  • MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
  • Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
  • OpenAI Provider: Native integration with OpenAI models

What is the Ashby MCP server, and what's possible with it?

The Ashby MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ashby account. It provides structured and secure access to your recruiting data, so your agent can perform actions like managing job postings, tracking candidate progress, scheduling interviews, and generating hiring reports on your behalf.

  • Automated job posting management: Easily create, update, or close job listings across your organization with direct agent assistance.
  • Candidate pipeline tracking: Have your agent fetch, organize, and update candidate progress through every stage of the hiring process.
  • Interview scheduling and coordination: Let your agent schedule interviews, send calendar invites, and manage interviewer assignments to streamline the process.
  • Data-driven hiring analytics: Generate reports and insights about your hiring funnel, candidate sources, and time-to-hire with a simple agent request.
  • Centralized communication with applicants: Enable your agent to send status updates, feedback, or reminders to candidates, keeping everyone in the loop automatically.

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 you begin, make sure you have:
  • Node.js and npm installed
  • A Composio account with API key
  • An OpenAI API key
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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.
3

Install required dependencies

bash
npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv

First, install the necessary packages for your project.

What you're installing:

  • @ai-sdk/openai: Vercel AI SDK's OpenAI provider
  • @ai-sdk/mcp: MCP client for Vercel AI SDK
  • @composio/core: Composio SDK for tool integration
  • ai: Core Vercel AI SDK
  • dotenv: Environment variable management
4

Set up environment variables

bash
OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

Create a .env file in your project root.

What's needed:

  • OPENAI_API_KEY: Your OpenAI API key for GPT model access
  • COMPOSIO_API_KEY: Your Composio API key for tool access
  • COMPOSIO_USER_ID: A unique identifier for the user session
5

Import required modules and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});
What's happening:
  • We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
  • The dotenv/config import automatically loads environment variables
  • The MCP client import enables connection to Composio's tool server
6

Create Tool Router session and initialize MCP client

typescript
async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["ashby"],
  });

  const mcpUrl = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Ashby tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned mcp object contains the URL and authentication headers needed to connect to the MCP server
  • This session provides access to all Ashby-related tools through the MCP protocol
7

Connect to MCP server and retrieve tools

typescript
const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();
What's happening:
  • We're creating an MCP client that connects to our Composio Tool Router session via HTTP
  • The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
  • The type: "http" is important - Composio requires HTTP transport
  • tools() retrieves all available Ashby tools that the agent can use
8

Initialize conversation and CLI interface

typescript
let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to ashby, like summarize my last 5 emails, send an email, etc... :)))\n",
);

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();
What's happening:
  • We initialize an empty messages array to maintain conversation history
  • A readline interface is created to accept user input from the command line
  • Instructions are displayed to guide the user on how to interact with the agent
9

Handle user input and stream responses with real-time tool feedback

typescript
rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({ role: "user", content: trimmedInput });
  console.log("\nAgent is thinking...\n");

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • We use streamText instead of generateText to stream responses in real-time
  • toolChoice: "auto" allows the model to decide when to use Ashby tools
  • stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
  • onStepFinish callback displays which tools are being used in real-time
  • We iterate through the text stream to create a typewriter effect as the agent responds
  • The complete response is added to conversation history to maintain context
  • Errors are caught and displayed with helpful retry suggestions

Complete Code

Here's the complete code to get you started with Ashby and Vercel AI SDK:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["ashby"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to ashby, like summarize my last 5 emails, send an email, etc... :)))\n",
  );

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
      console.log("\nGoodbye!");
      rl.close();
      process.exit(0);
    }

    if (!trimmedInput) {
      rl.prompt();
      return;
    }

    messages.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

Conclusion

You've successfully built a Ashby agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.

Key features of this implementation:

  • Real-time streaming responses for a better user experience with typewriter effect
  • Live tool execution feedback showing which tools are being used as the agent works
  • Dynamic tool loading through Composio's Tool Router with secure authentication
  • Multi-step tool execution with configurable step limits (up to 10 steps)
  • Comprehensive error handling for robust agent execution
  • Conversation history maintenance for context-aware responses

You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

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

Add Candidate to Project

Add a candidate to a project in Ashby.

Add Candidate Tag

Add a tag to a candidate in Ashby.

Add Hiring Team Member

Add an Ashby user to a hiring team at the application, job, or opening level.

Add User to Interviewer Pool

Add a user to an interviewer pool.

Add Opening Job

Adds a job to an opening (job requisition) in Ashby ATS.

Add Opening Location

Tool to add a location to an opening (job requisition).

Anonymize Candidate

Anonymize a candidate by removing personally identifiable information.

Approve Offer

Approve an offer or a specific approval step within an offer's approval process.

Archive Department

Archive a department by its unique identifier.

Archive Interviewer Pool

Archive an interviewer pool in Ashby.

Archive Location

Archives a location or location hierarchy in Ashby.

Change Application Source

Change the source attribution of an application.

Change Application Stage

Move an application to a different interview stage in the hiring pipeline.

Create Application

Create a new job application by associating a candidate with a job opening in Ashby ATS.

Create Candidate

Create a new candidate in the system.

Create Candidate Note

Create a note on a candidate profile.

Create Candidate Tag

Create a new candidate tag in Ashby for categorizing and organizing candidates.

Create Custom Field

Create a new custom field in Ashby.

Create Department

Create a new department.

Create Interviewer Pool

Create a new interviewer pool.

Create Job

Create a new job opening in Ashby ATS.

Create Location

Create a new location or location hierarchy.

Create Offer

Create a new offer for a candidate in Ashby ATS.

Create Opening

Create a new opening (job requisition) in Ashby ATS.

Create Referral

Create a referral in Ashby ATS by submitting a referral form with candidate information.

Create Survey Request

Generate a survey request and receive a survey URL to send to a candidate.

Create Survey Submission

Create a new survey submission for a candidate's application.

Get API Key Info

Retrieve information about the current API key, including associated organization, user details, and permissions.

Get Application Info

Retrieve detailed information about a specific application by its ID.

Get Candidate Info

Retrieve detailed information about a specific candidate by their ID.

Get Custom Field Info

Retrieve detailed information about a specific custom field by its ID.

Get Department Info

Retrieve detailed information about a specific department by its ID.

Get Feedback Form Definition

Retrieve detailed information about a specific feedback form definition by its ID.

Get File Info

Retrieve the URL of a file associated with a candidate.

Get Interviewer Pool Info

Retrieve detailed information about a specific interviewer pool by its ID.

Get Interviewer User Settings

Get interviewer settings for a specific user by their ID.

Get Interview Info

Retrieve detailed information about a specific interview type by its ID.

Get Interview Stage Info

Tool to fetch interview stage details by ID.

Get Job Info

Retrieve detailed information about a specific job by its ID.

Get Job Interview Plan Info

Retrieve the interview plan information for a specific job.

Get Job Posting Info

Retrieve detailed information about a specific job posting by its ID.

Get Location Info

Retrieve detailed information about a specific location by its ID.

Get Offer Info

Retrieve detailed information about a specific offer by its ID.

Get Opening Info

Retrieve detailed information about a specific opening (job requisition) by its ID.

Get Referral Form

Fetches the default referral form or creates a default referral form if none exists.

Get Survey Form Definition

Retrieve detailed information about a specific survey form definition by its ID.

Get User Info

Retrieve detailed information about a specific user by their ID.

List Application Criteria Evaluations

Retrieve AI-generated criteria evaluations for an application.

List Application Feedback

Retrieve all feedback submissions for an application.

List Application Hiring Team Roles

Retrieve all available hiring team roles for applications in the organization.

List Application History

Retrieve the complete history of stage transitions for an application.

List Applications

Retrieve a list of applications with optional pagination and sync-token filtering for incremental updates.

List Approvals

Retrieve a list of approvals (offer approvals, job approvals, etc.

List Archive Reasons

Retrieve a list of all archive reasons.

List Brands

Retrieve a list of all brands for the organization.

List Candidate Client Info

Retrieve all client info records for a specific candidate with pagination support.

List Candidate Notes

Retrieve all notes for a specific candidate in Ashby.

List Candidate Projects

Retrieve all projects associated with a candidate.

List Candidates

Retrieve a list of candidates.

List Candidate Tags

Retrieve a list of all candidate tags in your Ashby account.

List Close Reasons

Lists all close reasons for jobs or openings.

List Communication Templates

Retrieve a list of all communication templates.

List Custom Fields

Retrieve a list of all custom field definitions configured in Ashby.

List Departments

Retrieve a list of all departments in the organization.

List Feedback Form Definitions

Retrieve all feedback form definitions from your Ashby organization.

List Hiring Team Roles

Retrieve a list of possible hiring team roles in the organization.

List Interviewer Pools

Retrieve a list of all interviewer pools.

List Interview Events

Retrieves all interview events for a specific interview schedule.

List Interview Plans

Retrieve a list of interview plans.

List Interview Types

List all interview types defined in Ashby.

List Interview Schedules

Retrieve a list of interview schedules.

List Interview Stage Groups

Retrieve a list of interview stage groups.

List Interview Stages

Retrieve all interview stages for an interview plan in order.

List Job Boards

Retrieve a list of job boards.

List Job Postings

Retrieve a list of job postings.

List Jobs

Retrieve a list of all jobs from Ashby ATS (Applicant Tracking System).

List Job Templates

Retrieve a list of all job templates from Ashby ATS.

List Locations

Retrieve a list of all locations.

List Offers

Retrieve a list of job offers with their latest versions.

List Openings

Retrieve a list of openings (job requisitions).

List Projects

Retrieve a list of all projects.

List Sources

Retrieve a list of all candidate sources.

List Source Tracking Links

Retrieve all source tracking links configured in Ashby.

List Survey Form Definitions

Retrieve a list of all survey form definitions from Ashby.

List Survey Submissions

Lists all survey submissions of a given survey type from Ashby.

List Users

Retrieve a list of all users in the organization.

Move Department

Tool to move a department to another parent in the organizational hierarchy.

Move Location

Tool to move a location to a different parent in the location hierarchy.

Remove Hiring Team Member

Remove an Ashby user from a hiring team at the application, job, or opening level.

Remove User from Interviewer Pool

Remove a user from an interviewer pool.

Remove Opening Job

Remove a job from an opening (job requisition) in Ashby ATS.

Remove Opening Location

Tool to remove a location from an opening (job requisition).

Restore Department

Restore an archived department by its unique identifier.

Restore Interviewer Pool

Restore an archived interviewer pool in Ashby.

Restore Location

Restores an archived location or location hierarchy in Ashby.

Search Candidates

Search for candidates by email or name.

Search Jobs

Search for jobs by title in Ashby ATS (Applicant Tracking System).

Search Opening

Search for openings by identifier.

Search Projects

Search for projects by title in Ashby.

Search Users

Search for an Ashby user by email address.

Set Custom Field Value

Set the value of a custom field for a given object (candidate, application, job, etc.

Set Custom Field Values

Set the values of multiple custom fields for a given object in a single call.

Set Job Status

Set the status of a job in Ashby ATS (Applicant Tracking System).

Set Opening Archived

Sets the archived state of an opening.

Set Opening State

Set the workflow state of an opening (job requisition).

Start Offer

Create a new offer version instance for an in-progress offer process.

Start Offer Process

Start an offer process for a candidate's application in Ashby ATS.

Submit Application Feedback

Submit structured feedback for an application using a feedback form.

Transfer Application

Transfer an application to a different job position in Ashby ATS.

Update Application

Update an application's properties in Ashby.

Update Application History

Update the complete history of an application's stage transitions.

Update Candidate

Update an existing candidate's profile information in Ashby ATS.

Update Job Compensation

Update a job's compensation tiers in Ashby ATS.

Update Department

Update an existing department's information such as its name.

Update Interviewer Pool

Update an existing interviewer pool's title or training requirements.

Update Job

Update an existing job's properties in Ashby ATS.

Update Job Posting

Update an existing job posting's details including title, description, and visibility status.

Update Location Address

Update the address of a location or location hierarchy.

Update Location External Name

Update a location's external (candidate-facing) name.

Update Location Name

Update a location's name.

Update Location Remote Status

Tool to update a location's remote status.

Update Location Workplace Type

Tool to update a location's workplace type (OnSite, Remote, or Hybrid).

Update Opening

Update properties of an existing opening (job requisition).

Update Selectable Values Custom Field

Update the selectable values for a ValueSelect or MultiValueSelect custom field.

Update User Interviewer Settings

Update interviewer settings for a user, including daily and weekly interview limits.

FRAMEWORKS

How to build Ashby MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Ashby MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Ashby MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Ashby MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Ashby MCP with Claude Cowork

Codex logo

Codex

Use Ashby MCP with Codex

OpenClaw logo

OpenClaw

Use Ashby MCP with OpenClaw

Hermes logo

Hermes

Use Ashby MCP with Hermes

CLI logo

CLI

Use Ashby MCP with CLI

Google ADK logo

Google ADK

Use Ashby MCP with Google ADK

LangChain logo

LangChain

Use Ashby MCP with LangChain

Mastra AI logo

Mastra AI

Use Ashby MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Ashby MCP with LlamaIndex

CrewAI logo

CrewAI

Use Ashby MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Ashby MCP server, the agents and LLMs can only access a fixed set of Ashby tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ashby and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Vercel AI SDK v6 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 Ashby tools.

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

Start with Ashby.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Ashby 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