How to integrate Esputnik MCP with LlamaIndex

This guide walks you through connecting Esputnik to LlamaIndex using the Composio tool router. By the end, you'll have a working Esputnik agent that can bulk add 500 new email contacts, delete sms message template with id 123, get status of yesterday's contact import through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Esputnik account through Composio's Esputnik 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
Esputnik logoEsputnik
Api Key

eSputnik is a marketing automation platform for managing emails, SMS, and push notifications. It helps businesses streamline customer communications across multiple channels.

89 Tools

Introduction

This guide walks you through connecting Esputnik to LlamaIndex using the Composio tool router. By the end, you'll have a working Esputnik agent that can bulk add 500 new email contacts, delete sms message template with id 123, get status of yesterday's contact import through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Esputnik account through Composio's Esputnik MCP server.

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

Also integrate Esputnik with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAI

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 Esputnik
  • Connect LlamaIndex to the Esputnik MCP server
  • Build a Esputnik-powered agent using LlamaIndex
  • Interact with Esputnik 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 Esputnik MCP server, and what's possible with it?

The Esputnik MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Esputnik account. It provides structured and secure access to your marketing automation tools, so your agent can perform actions like sending broadcasts, managing contacts, importing data, and handling push notifications on your behalf.

  • Bulk contact import and management: Quickly add or update thousands of contacts at once, check import status, and keep your lists up to date with minimal effort.
  • Broadcast and message control: Retrieve, review, and manage your marketing broadcasts and app inbox messages, ensuring your campaigns run smoothly.
  • Order and transactional data automation: Import and synchronize large batches of order data, keeping your marketing segmentation and triggers accurate and relevant.
  • Push and SMS notification management: Activate or deactivate push tokens, delete outdated SMS templates, and fine-tune your notification workflows directly through your agent.
  • Domain and integration setup: Register domains for web tracking or widgets, helping you expand and customize your communication reach seamlessly.

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 step10 STEPS
1

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 Esputnik account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Esputnik

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
3

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
4

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 Esputnik access
5

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 esputnik_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
6

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.

7

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: ["esputnik"],
    },
  );

  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 Esputnik 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, esputnik)
  • 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 Esputnik tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

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 Esputnik
  • 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 Esputnik 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
9

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 Esputnik
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with Esputnik 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: ["esputnik"],
    },
  );

  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 Esputnik 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 Esputnik to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Esputnik 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 Esputnik action and event your agent gets out of the box.

Add Contact

Tool to create or update a single contact in eSputnik in real-time.

Add Domain

Register a domain with eSputnik for web tracking, widgets, or web push notifications.

Add Orders Bulk

Tool to transfer orders in bulk to eSputnik.

Add Unsubscribed Emails

Tool to add email addresses to the list of unsubscribed contacts.

Add Web Push Domain

Tool to add a domain for web push notifications in eSputnik.

Attach Contacts to Segment

Tool to attach contacts to a static segment (group) by contact IDs or external customer IDs.

Bulk Add or Update Contacts

Bulk add or update up to 3000 contacts in eSputnik asynchronously.

Change Mobile Push Token Activity

Activate or deactivate a mobile push notification token in eSputnik.

Create API Token

Generate a new API token for authentication.

Create App Inbox Message

Tool to create a basic App Inbox message in eSputnik.

Create Contacts from File

Import or update contacts from an external file in eSputnik.

Create Email Message

Tool to create or update an email message in eSputnik.

Create Mobile Push Message

Tool to create a new mobile push notification message in eSputnik.

Create SMS Message

Tool to create a basic SMS message template in eSputnik.

Create Telegram Message

Create a basic Telegram bot message in eSputnik.

Delete App Inbox Message

Tool to delete an App Inbox message by its ID from eSputnik.

Delete App Inbox Translation

Delete a language translation of an App Inbox message from eSputnik.

Delete Broadcast

Tool to cancel a scheduled broadcast campaign.

Delete Contact

Tool to delete a contact by its Yespo ID.

Delete Contact by External ID

Delete a contact from eSputnik using their external customer ID.

Delete Email Message

Delete a basic email message by its ID from eSputnik.

Delete Email Translation

Delete a translation of a base email message from eSputnik.

Delete Mobile Push Message

Delete a base Mobile Push message by its ID from eSputnik.

Delete Mobile Push Translation

Delete a language version of a base Mobile Push message from eSputnik.

Delete Orders

Tool to schedule asynchronous deletion of orders in eSputnik.

Delete SMS Message

Delete a base SMS message template by its ID from eSputnik.

Delete SMS Translation

Delete a language version of a base SMS message from eSputnik.

Delete Telegram Message

Delete a base Telegram bot message by its ID from eSputnik.

Delete Telegram Translation

Delete a language version of a Telegram bot message from eSputnik.

Detach Contacts from Segment

Tool to delete contacts from a static segment by contact IDs or external customer IDs.

Generate Event V2

Tool to send backend events from websites and mobile apps to eSputnik.

Generate Event V3

Tool to generate events in eSputnik v3 API.

Generate Past Events V2

Tool to transfer past event data from your CRM or data store to eSputnik using v2 API.

Generate Past Events V3

Tool to generate past events in eSputnik v3 API.

Get Account Info

Retrieve basic eSputnik account information.

Get App Inbox Message

Retrieves an App Inbox message by its unique identifier from eSputnik.

Get Broadcasts

Retrieve a paginated list of broadcast campaigns from eSputnik.

Get Contact

Retrieve complete information about a contact by their ID.

Get Contact Emails

Tool to retrieve email addresses of contacts by their contact IDs.

Get Contact Import Status

Retrieve the status of a contact import session in eSputnik.

Get Contact Message History

Retrieve a contact's message history across multiple channels from eSputnik.

Get Contacts

Search for contacts in eSputnik using various filter criteria.

Get Contact Subscriptions

Retrieve all subscription categories a contact is enrolled in.

Get Email Interfaces

Tool to retrieve all configured email interfaces (sender names) from eSputnik.

Get Email Message

Retrieves an email message by its unique identifier from eSputnik.

Get Email View Link

Get a link to view an email message in browser from eSputnik.

Get Message Status

Retrieve delivery status for sent messages across all channels (email, SMS, Viber, push).

Get Mobile Push Message

Retrieves a mobile push message by its unique identifier from eSputnik.

Get Organization Balance

Retrieve the current eSputnik organization balance.

Get Organization Billing History

Retrieve the organization's billing history from eSputnik, broken down by day and media channel.

Get Preprocessor File Status

Retrieve the status of a preprocessor file upload session.

Get Product Feeds Configuration

Tool to retrieve product feeds configuration from eSputnik.

Get Promocodes Count

Get the number of available promotional codes in eSputnik.

Get Site Domain

Retrieve the organization's domain configuration from eSputnik.

Get Site Tracking Script

Retrieve the site tracking script for your eSputnik account.

Get SMS Interfaces

Retrieve all SMS interfaces (alpha names) configured for the organization.

Get Subscription Categories

Retrieve all subscription categories for the organization.

Get Telegram Message

Retrieve a Telegram bot message by its unique identifier from eSputnik.

List Promotional Codes

Retrieve a list of promotional codes from eSputnik.

List Web Push Domains

Retrieve the list of domains registered for web push notifications.

Remove From Unsubscribed

Tool to remove email addresses from the unsubscribed contacts list in eSputnik.

Search App Inbox Messages

Search for mobile App Inbox messages using a part of the name or a tag.

Search Contacts

Search for all contacts in a segment (group).

Search Email Messages

Search for email messages using a part of their name or a tag.

Search Mobile Push Messages

Search for mobile push messages using part of the name or a tag.

Search Segments

Search for and retrieve available segments (groups) in eSputnik.

Search SMS Messages

Search for SMS messages using part of their names or tags in eSputnik.

Search Telegram Messages

Search for Telegram bot messages using a part of name or a tag.

Search Viber Messages

Search for Viber messages using part of the name or a tag.

Search Workflows

Search for and retrieve available workflows from eSputnik.

Send Email

Send an email message to one or more contacts via eSputnik API.

Send Prepared Message

Tool to send a prepared message to one or many contacts.

Subscribe Contact

Tool to subscribe a contact for double opt-in implementation.

Update App Inbox Message

Tool to update the base App Inbox message in eSputnik.

Update App Inbox Translation

Tool to update or add a language version for an App Inbox message in eSputnik.

Update Contact

Tool to update contact information by contact ID.

Update Contact Subscriptions

Tool to update the subscription categories a contact is enrolled in.

Update Email Message

Tool to update an existing email message in eSputnik.

Update Email Translation

Tool to update or add a language version for a base email message in eSputnik.

Update Interaction Status

Tool to update the status of a message interaction using interaction_id.

Update Mobile Push Message

Tool to update an existing mobile push notification message in eSputnik.

Update Mobile Push Translation

Tool to update or add a language version for a mobile push message in eSputnik.

Update Preprocessor File By ID

Tool to update a preprocessor file's data by providing a new external link.

Update SMS Message

Tool to update an existing base SMS message template in eSputnik.

Update SMS Translation

Tool to update a language version of an SMS message in eSputnik.

Update Telegram Message

Update a base Telegram bot message in eSputnik.

Update Telegram Translation

Update a translated telegram bot message in eSputnik.

Upload Preprocessor File

Tool to upload a file for the preprocessor from an external repository.

Upload Promotional Codes

Tool to upload promotional codes to eSputnik in bulk.

FRAMEWORKS

How to build Esputnik MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Esputnik MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Esputnik MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Esputnik MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Esputnik MCP with Claude Cowork

Codex logo

Codex

Use Esputnik MCP with Codex

OpenClaw logo

OpenClaw

Use Esputnik MCP with OpenClaw

Hermes logo

Hermes

Use Esputnik MCP with Hermes

CLI logo

CLI

Use Esputnik MCP with CLI

Google ADK logo

Google ADK

Use Esputnik MCP with Google ADK

LangChain logo

LangChain

Use Esputnik MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Esputnik MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Esputnik MCP with Mastra AI

CrewAI logo

CrewAI

Use Esputnik MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Esputnik MCP server, the agents and LLMs can only access a fixed set of Esputnik tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Esputnik 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 Esputnik tools.

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

Start with Esputnik.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Esputnik 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
Esputnik MCP Integration with LlamaIndex | Composio