How to integrate Mailerlite MCP with LlamaIndex

This guide walks you through connecting Mailerlite to LlamaIndex using the Composio tool router. By the end, you'll have a working Mailerlite agent that can create a new subscriber group called vip customers, add a custom field for subscriber birthday, create a segment for recent e-commerce buyers through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Mailerlite account through Composio's Mailerlite 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
Mailerlite logoMailerlite
Api Key

MailerLite is an email marketing service for building, sending, and automating campaigns. It helps businesses reach audiences with beautiful emails, landing pages, and advanced automation.

86 Tools

Introduction

This guide walks you through connecting Mailerlite to LlamaIndex using the Composio tool router. By the end, you'll have a working Mailerlite agent that can create a new subscriber group called vip customers, add a custom field for subscriber birthday, create a segment for recent e-commerce buyers through natural language commands.

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

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

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

The Mailerlite MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mailerlite account. It provides structured and secure access to your email marketing tools, so your agent can create campaigns, manage subscribers, automate workflows, and oversee your shop integrations with ease.

  • Campaign automation and workflow management: Instruct your agent to create or delete automations, streamlining your email marketing processes and ensuring timely communication with your audience.
  • E-commerce customer and shop integration: Let your agent create, update, or remove e-commerce customers and shops for seamless sales tracking, customer onboarding, or data syncing.
  • Subscriber group and segment organization: Have your agent create custom fields, new subscriber groups, or targeted segments so you can send highly personalized campaigns.
  • Webhook registration for real-time updates: Direct your agent to set up webhooks for specific events, enabling instant notifications and integrations with other systems as actions happen in Mailerlite.
  • Efficient cleanup and management: Ask your agent to delete outdated automations, customers, or shops, helping you keep your Mailerlite workspace organized and up to date.

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

Getting API Keys for OpenAI, Composio, and Mailerlite

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

  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 Mailerlite 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, mailerlite)
  • 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 Mailerlite 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 Mailerlite
  • 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 Mailerlite 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 Mailerlite
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

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

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

Add Product to Category

Tool to add a product to a category in an e-commerce shop.

Add Subscriber To Group

Tool to assign an existing subscriber to a group.

Create automation

Create automation

Create Campaign

Tool to create a new email campaign (draft) with specified type, content, and targeting.

Create E-commerce Cart Item

Tool to add an item to a shopping cart.

Create E-commerce Category

Tool to create a new product category for a shop.

Create/Update E-commerce Customer

Tool to create or update a customer record for a shop.

Create E-commerce Order

Tool to create a new order for a shop.

Create E-commerce Product

Tool to create a new product for an e-commerce shop.

Create E-commerce Shop

Tool to connect a new e-commerce shop.

Create Field

Tool to create a new custom field.

Create Group

Tool to create a new subscriber group.

Create Segment

Tool to create a new subscriber segment.

Create Subscriber

Tool to create or update (upsert) a subscriber by email.

Create Webhook

Tool to register a new webhook URL for specified event types.

Delete Automation

Tool to delete an automation workflow by ID.

Delete E-commerce Cart Item

Tool to remove an item from a cart in an e-commerce shop.

Delete E-commerce Category

Tool to delete a product category from an e-commerce shop by IDs.

Delete E-commerce Customer

Tool to delete a customer from an e-commerce shop by IDs.

Delete E-commerce Order

Tool to delete an order from a shop.

Delete E-commerce Product

Tool to delete a product from an e-commerce shop by IDs.

Delete E-commerce Shop

Tool to disconnect an e-commerce shop by ID.

Delete Field

Tool to delete a custom field.

Delete Group

Tool to delete a subscriber group by ID.

Delete Segment

Tool to delete a segment by ID.

Delete Subscriber

Tool to delete a subscriber by ID.

Delete Webhook

Tool to remove a webhook subscription by ID.

Execute Batch Request

Tool to execute multiple API requests in a single batch call (max 50 requests).

Forget Subscriber

Tool to forget a subscriber completely (GDPR compliant deletion).

Get Account Info

Tool to retrieve basic MailerLite account details.

Get Account Stats

Tool to retrieve usage statistics and performance metrics for the account.

Get Automation

Tool to retrieve details of a specific automation by ID.

Get Automation Activity

Tool to retrieve subscriber activity for a specific automation.

Get Campaign Languages

Tool to retrieve a list of all available campaign languages.

Get Campaigns

Tool to retrieve a list of all campaigns.

Get E-commerce Cart

Tool to fetch details of a specific cart by shop ID and cart ID.

Get E-commerce Cart Item

Tool to fetch details of a specific cart item by shop ID, cart ID, and item ID.

Get E-commerce Category

Tool to fetch details of a specific product category by shop and category ID.

Get E-commerce Customer

Tool to fetch details of a customer by shop and customer ID.

Get E-commerce Customers

Tool to list customers for a specific shop.

Get E-commerce Order

Tool to fetch details of a specific e-commerce order by shop ID and order ID.

Get E-commerce Product

Tool to fetch details of a specific e-commerce product by shop and product ID.

Get E-commerce Shop

Tool to fetch details of a specific e-commerce shop by ID.

Get E-commerce Shops

Tool to list all e-commerce shops connected to the account.

Get Fields

Tool to retrieve all custom fields defined in the account.

Get Group

Tool to retrieve details of a specific subscriber group by ID.

Get Groups

Tool to retrieve all subscriber groups.

Get Group Subscribers

Tool to list subscribers within a group by ID.

Get Import Status

Tool to retrieve the status and detailed report of a subscriber import operation by import ID.

Get Segment

Tool to retrieve a specific segment by ID.

Get Segments

Tool to retrieve all segments in the account.

Get Segment Subscribers

Tool to retrieve all subscribers belonging to a specific segment.

Get Subscriber

Tool to fetch a single subscriber by ID or email address.

Get Subscriber Activity

Tool to fetch the activity log for a specific subscriber.

Get Subscribers

Tool to retrieve all subscribers.

Get Subscribers Stats

Tool to get subscriber statistics for the account.

Get Webhook

Tool to retrieve details of a specific webhook by ID.

Get Webhooks

Tool to retrieve all configured webhooks.

Import E-commerce Categories

Tool to bulk import categories to an e-commerce shop.

Import E-commerce Orders

Tool to bulk import orders to an e-commerce shop.

Import E-commerce Products

Tool to bulk import products to an e-commerce shop.

Import Subscribers to Group

Tool to bulk import multiple subscribers to a specific group.

List Automations

Tool to retrieve all automations in your MailerLite account.

List E-commerce Cart Items

Tool to list all items in a specific cart for an e-commerce shop.

List E-commerce Carts

Tool to list all carts for a specific shop.

List E-commerce Categories

Tool to list all product categories for a shop.

List E-commerce Category Products

Tool to list all products in a specific e-commerce category.

List E-commerce Orders

Tool to list all orders for a specific e-commerce shop.

List E-commerce Products

Tool to list all products for a specific e-commerce shop.

List Forms

Tool to retrieve all forms of a specific type (popup, embedded, or promotion).

List Timezones

Tool to retrieve all available timezones supported by MailerLite.

Remove Product From Category

Tool to remove a product from a category in an e-commerce shop.

Remove Subscriber From Group

Tool to remove a subscriber from a group by ID.

Set Double Opt-In

Tool to enable or disable double opt-in for new subscribers.

Update E-commerce Cart

Tool to update an existing cart's checkout URL or total price.

Update E-commerce Cart Item

Tool to update a cart item's quantity or properties in an e-commerce cart.

Update E-commerce Category

Tool to update an existing product category in an e-commerce shop.

Update E-commerce Customer

Tool to update a customer's data for a shop by IDs.

Update E-commerce Order

Tool to update an existing order's status or total price in an e-commerce shop.

Update E-commerce Product

Tool to update an existing product in an e-commerce shop by IDs.

Update E-commerce Shop

Tool to update settings of a connected e-commerce shop by ID.

Update Field

Tool to update the title of an existing custom field.

Update Group

Tool to update a group's name by ID.

Update Segment

Tool to rename an existing segment by ID.

Update Subscriber

Tool to update an existing subscriber's information by ID.

Update Webhook

Tool to update an existing MailerLite webhook.

FRAMEWORKS

How to build Mailerlite MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Mailerlite MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Mailerlite MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Mailerlite MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Mailerlite MCP with Claude Cowork

Codex logo

Codex

Use Mailerlite MCP with Codex

OpenClaw logo

OpenClaw

Use Mailerlite MCP with OpenClaw

Hermes logo

Hermes

Use Mailerlite MCP with Hermes

CLI logo

CLI

Use Mailerlite MCP with CLI

Google ADK logo

Google ADK

Use Mailerlite MCP with Google ADK

LangChain logo

LangChain

Use Mailerlite MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Mailerlite MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Mailerlite MCP with Mastra AI

CrewAI logo

CrewAI

Use Mailerlite MCP with CrewAI

FAQ

Frequently asked questions

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

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

Start with Mailerlite.It takes 30 seconds.

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