# How to integrate Omnisend MCP with LlamaIndex

```json
{
  "title": "How to integrate Omnisend MCP with LlamaIndex",
  "toolkit": "Omnisend",
  "toolkit_slug": "omnisend",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/omnisend/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/omnisend/framework/llama-index.md",
  "updated_at": "2026-05-12T10:20:31.368Z"
}
```

## Introduction

This guide walks you through connecting Omnisend to LlamaIndex using the Composio tool router. By the end, you'll have a working Omnisend agent that can add new subscribers from latest signups, update contact email preferences in bulk, list all products for upcoming campaign through natural language commands.
This guide will help you understand how to give your LlamaIndex agent real control over a Omnisend account through Composio's Omnisend MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Omnisend with

- [OpenAI Agents SDK](https://composio.dev/toolkits/omnisend/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/omnisend/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/omnisend/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/omnisend/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/omnisend/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/omnisend/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/omnisend/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/omnisend/framework/cli)
- [Google ADK](https://composio.dev/toolkits/omnisend/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/omnisend/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/omnisend/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/omnisend/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/omnisend/framework/crew-ai)

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

The Omnisend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Omnisend account. It provides structured and secure access to your ecommerce marketing data, so your agent can manage contacts, automate batch operations, update products, and streamline campaign preparation for your store.
- Bulk contact and product management: Effortlessly create or update large sets of contacts or products in one go, perfect for onboarding new subscribers or syncing your catalog.
- Individual contact handling: Retrieve, update, or enrich detailed contact profiles, making it easy for your agent to personalize outreach or manage subscriptions.
- Batch job automation and tracking: Initiate batch operations and monitor their progress, status, and results to ensure smooth processing of large datasets.
- Product catalog maintenance: List, review, or delete products directly from your Omnisend account, keeping your store's offerings up to date for campaigns.
- Contact segmentation and filtering: Fetch paginated and filtered contact lists, enabling targeted marketing actions and smarter audience management.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `OMNISEND_ADD_CART_PRODUCT` | Add Cart Product | Tool to add a product to a cart in Omnisend (v3 API). Use when updating cart contents or tracking abandoned carts. |
| `OMNISEND_CREATE_BATCH` | Create Batch | Tool to create a new batch operation for multiple items. Use when you need to process many records asynchronously in one call, e.g., bulk contacts, products, orders, or events. Use after preparing the items list to avoid rate limits. |
| `OMNISEND_CREATE_CART` | Create Cart | Tool to create a new shopping cart in Omnisend. Use when tracking customer cart activity for abandoned cart campaigns. |
| `OMNISEND_CREATE_CATEGORY` | Create Category | Tool to create a new category in Omnisend. Use when organizing products into categories. |
| `OMNISEND_CREATE_ORDER` | Create Order | Tool to create a new order in Omnisend v3 API. Use when recording a customer purchase or order transaction. |
| `OMNISEND_CREATE_OR_UPDATE_CONTACT` | Create or Update Contact | Tool to create or update a contact in Omnisend. Use after collecting subscriber details. |
| `OMNISEND_CREATE_PRODUCT` | Create Product | Tool to create a new product in the Omnisend product catalog. Use when adding products for email campaigns or syncing inventory. |
| `OMNISEND_CREATE_PRODUCT_CATEGORY` | Create Product Category | Tool to create a new product category in the Omnisend catalog. Use when organizing products into categories. |
| `OMNISEND_DELETE_CART` | Delete Cart | Tool to delete a cart from Omnisend by its ID (v3 API). Use when you need to remove an abandoned or expired cart from the system. |
| `OMNISEND_DELETE_CATEGORY` | Delete Category | Tool to remove a category from Omnisend by its ID. Use when you need to delete a category and ensure it is no longer available in your catalog. |
| `OMNISEND_DELETE_ORDER` | Delete Order | Tool to delete an order from Omnisend by its ID. Use when you need to remove an order from the system. |
| `OMNISEND_DELETE_PRODUCT` | Delete Product | Tool to remove a product from Omnisend by its ID. Use when you need to delete a product and ensure it is no longer available in your catalog. |
| `OMNISEND_DELETE_PRODUCT_CATEGORY` | Delete Product Category | Tool to remove a product category from Omnisend by its ID. Use when you need to delete a product category from your catalog. |
| `OMNISEND_GET_BATCHES` | Get Batches | Tool to retrieve a list of batch operations. Use after initiating a batch job to monitor its progress and results. |
| `OMNISEND_GET_BATCH_INFORMATION` | Get Batch Information | Tool to retrieve information about a specific batch by ID. Use after submitting a batch when you need a detailed status and counts. |
| `OMNISEND_GET_BATCH_ITEM` | Get Batch Item | Tool to retrieve a specific item within a batch by batchID and itemID. Use when you need to inspect the result of a single batch operation. |
| `OMNISEND_GET_BATCH_ITEMS` | Get Batch Items | Tool to retrieve processed items of a specific batch by ID. Use when you need to inspect individual results of a batch operation after fetching batch details. |
| `OMNISEND_GET_BRAND` | Get Brand | Tool to retrieve information about the current authenticated brand. Use when you need brand details like currency, platform, or website. |
| `OMNISEND_GET_CART` | Get Cart | Tool to retrieve a specific cart by ID from Omnisend v3 API. Use when you need detailed cart information including products and customer contact details. |
| `OMNISEND_GET_CATEGORY` | Get Category | Tool to retrieve details of a specific category by ID. Use when you need to fetch information about a category. |
| `OMNISEND_GET_CONTACT` | Get Contact | Tool to retrieve details of a single contact by ID. Use when you already have a contactId and need the full profile. |
| `OMNISEND_GET_ORDER` | Get Order | Tool to retrieve details of a specific order by ID. Use when you need order information including products, addresses, and payment details. |
| `OMNISEND_GET_PRODUCT` | Get Product | Tool to retrieve details of a specific product by ID from Omnisend. Use when you need full product information including variants, pricing, and stock status. |
| `OMNISEND_GET_PRODUCT_CATEGORY` | Get Product Category | Tool to retrieve a specific product category by ID. Use when you need details about a particular product category. |
| `OMNISEND_LIST_CAMPAIGNS` | List Campaigns | Tool to retrieve a paginated list of campaigns with optional filtering by status and type. Use when you need to view or analyze campaign performance across multiple campaigns. |
| `OMNISEND_LIST_CARTS` | List Carts | Tool to retrieve a paginated list of carts with optional filtering. Use when you need to fetch carts by date range, contact, or segment. |
| `OMNISEND_LIST_CATEGORIES` | List Categories | Tool to retrieve a paginated list of product categories. Use when you need category IDs for product management or catalog organization. |
| `OMNISEND_LIST_CONTACTS` | List Contacts | Tool to retrieve a paginated list of contacts with optional filtering. Use when you need to fetch contacts in batches and handle cursor pagination. |
| `OMNISEND_LIST_EVENTS` | List Events | Tool to retrieve all custom events created in Omnisend app. Use when you need to view available event types for automation workflows or event tracking. |
| `OMNISEND_LIST_PRODUCT_CATEGORIES` | List Product Categories | Tool to retrieve a paginated list of product categories from the Omnisend catalog. Use when fetching category data for product organization. |
| `OMNISEND_LIST_PRODUCTS` | List Products | Tool to retrieve a paginated list of products. Use when syncing product catalog before campaign creation. |
| `OMNISEND_REMOVE_CART_PRODUCT` | Remove Cart Product | Tool to remove a product from a cart in Omnisend. Use when you need to delete a specific product from a cart. |
| `OMNISEND_REPLACE_CART` | Replace Cart | Tool to replace an existing cart in Omnisend using the v3 API. Use when you need to completely replace all cart data including products, pricing, and recovery URL. |
| `OMNISEND_REPLACE_CART_PRODUCT` | Replace Cart Product | Tool to replace a product in a cart using Omnisend v3 API. Use when you need to update all details of a specific product in a cart. |
| `OMNISEND_REPLACE_CATEGORY` | Replace Category | Tool to replace a category's title by ID. Use when you need to update an entire category resource. |
| `OMNISEND_REPLACE_ORDER` | Replace Order | Tool to completely replace an existing order in Omnisend. Use when you need to update all order details at once, replacing the entire order record. |
| `OMNISEND_REPLACE_PRODUCT` | Replace Product | Tool to replace an existing product in the Omnisend catalog. Use when you need to completely replace all product data with new information. |
| `OMNISEND_SEND_EVENT` | Send Event | Tool to send a customer event to Omnisend. Events can trigger automations and track customer behavior. Use when you need to record customer interactions such as product views, cart actions, or custom events. |
| `OMNISEND_UPDATE_CART` | Update Cart | Tool to partially update a cart in Omnisend (v3 API). Use when you need to modify cart details such as currency, total amount, recovery URL, or products. |
| `OMNISEND_UPDATE_CART_PRODUCT` | Update Cart Product | Tool to update a product in a cart (v3 API). Use when you need to modify product details such as quantity, price, or other attributes for an existing cart item. |
| `OMNISEND_UPDATE_CONTACT` | Update Contact | Tool to update fields of an existing contact by ID. Use after retrieving contact ID. PATCH https://api.omnisend.com/v3/contacts/{contactId} Example: UpdateContact(contactId="..., body={firstName: 'John'}) |
| `OMNISEND_UPDATE_ORDER_STATUS` | Update Order Status | Tool to partially update an order status in Omnisend (v3 API). Use when you need to update shipping details, payment status, or fulfillment status of an existing order. |
| `OMNISEND_UPDATE_PRODUCT_CATEGORY` | Update Product Category | Tool to update an existing product category title in Omnisend. Use when you need to modify a category's name. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Omnisend MCP server is an implementation of the Model Context Protocol that connects your AI agent to Omnisend. It provides structured and secure access so your agent can perform Omnisend operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 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 Omnisend account and project
- Basic familiarity with async Python/Typescript

### 1. Getting API Keys for OpenAI, Composio, and Omnisend

No description provided.

### 2. Installing dependencies

No description provided.
```python
pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv
```

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

### 3. Set environment variables

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 Omnisend access
```bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id
```

### 4. Import modules

No description provided.
```python
import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()
```

```typescript
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();
```

### 5. Load environment variables and initialize Composio

No description provided.
```python
OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set in the environment")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment")
```

```typescript
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");
```

### 6. Create a Tool Router session and build the agent function

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, omnisend)
- 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 Omnisend tools.
- The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
```python
async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["omnisend"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Omnisend actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Omnisend actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)
```

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

  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 Omnisend actions." ,
    llm,
    tools,
  });

  return agent;
}
```

### 7. Create an interactive chat loop

No description provided.
```python
async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")
```

```typescript
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();
}
```

### 8. Define the main entry point

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 Omnisend
```python
async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")
```

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

main();
```

### 9. Run the agent

When prompted, authenticate and authorise your agent with Omnisend, then start asking questions.
```bash
python llamaindex_agent.py
```

```typescript
npx ts-node llamaindex-agent.ts
```

## Complete Code

```python
import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

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

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["omnisend"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Omnisend actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Omnisend actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")
```

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

  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 Omnisend 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 Omnisend to LlamaIndex through Composio's Tool Router MCP layer.
Key takeaways:
- Tool Router dynamically exposes Omnisend 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.

## How to build Omnisend MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/omnisend/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/omnisend/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/omnisend/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/omnisend/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/omnisend/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/omnisend/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/omnisend/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/omnisend/framework/cli)
- [Google ADK](https://composio.dev/toolkits/omnisend/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/omnisend/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/omnisend/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/omnisend/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/omnisend/framework/crew-ai)

## Related Toolkits

- [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing.
- [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages.
- [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections.
- [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach.
- [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease.
- [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic.
- [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns.
- [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active.
- [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place.
- [Bigmailer](https://composio.dev/toolkits/bigmailer) - BigMailer is an email marketing platform for managing multiple brands with white-labeling and automation. It helps teams streamline campaigns and simplify integration with Amazon SES.
- [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere.
- [Brevo](https://composio.dev/toolkits/brevo) - Brevo is an all-in-one email and SMS marketing platform for transactional messaging, automation, and CRM. It helps businesses engage customers and streamline communications through powerful campaign tools.
- [Campayn](https://composio.dev/toolkits/campayn) - Campayn is an email marketing platform for creating, sending, and managing campaigns. It helps businesses engage contacts and grow audiences with easy-to-use tools.
- [Cardly](https://composio.dev/toolkits/cardly) - Cardly is a platform for creating and sending personalized direct mail to customers. It helps businesses break through the digital clutter by getting real engagement via physical mailboxes.
- [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management.
- [Crustdata](https://composio.dev/toolkits/crustdata) - CrustData is an AI-powered data intelligence platform for real-time company and people data. It helps B2B sales teams, AI SDRs, and investors react to live business signals.
- [Curated](https://composio.dev/toolkits/curated) - Curated is a platform for collecting, curating, and publishing newsletters. It streamlines content aggregation and distribution for creators and teams.
- [Customerio](https://composio.dev/toolkits/customerio) - Customer.io is a customer engagement platform for targeted messaging across email, SMS, and push. Easily automate, segment, and track communications with your audience.
- [Cutt ly](https://composio.dev/toolkits/cutt_ly) - Cutt.ly is a URL shortening service for managing and analyzing links. Streamline your workflows with quick, trackable, and branded short URLs.
- [Demio](https://composio.dev/toolkits/demio) - Demio is webinar software built for marketers, offering both live and automated sessions with interactive features. It helps teams engage audiences and optimize lead generation through detailed analytics.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Omnisend MCP?

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

### Can I use Tool Router MCP with LlamaIndex?

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

### Can I manage the permissions and scopes for Omnisend while using Tool Router?

Yes, absolutely. You can configure which Omnisend 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.

### How safe is my data with Composio Tool Router?

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 Omnisend data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)