# How to integrate Moosend MCP with LlamaIndex ```json { "title": "How to integrate Moosend MCP with LlamaIndex", "toolkit": "Moosend", "toolkit_slug": "moosend", "framework": "LlamaIndex", "framework_slug": "llama-index", "url": "https://composio.dev/toolkits/moosend/framework/llama-index", "markdown_url": "https://composio.dev/toolkits/moosend/framework/llama-index.md", "updated_at": "2026-05-12T10:19:27.420Z" } ``` ## Introduction This guide walks you through connecting Moosend to LlamaIndex using the Composio tool router. By the end, you'll have a working Moosend agent that can add new subscriber to welcome list, get all campaigns sent last month, retrieve details for summer sale campaign through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Moosend account through Composio's Moosend MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Moosend with - [OpenAI Agents SDK](https://composio.dev/toolkits/moosend/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/moosend/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/moosend/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/moosend/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/moosend/framework/codex) - [OpenClaw](https://composio.dev/toolkits/moosend/framework/openclaw) - [Hermes](https://composio.dev/toolkits/moosend/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/moosend/framework/cli) - [Google ADK](https://composio.dev/toolkits/moosend/framework/google-adk) - [LangChain](https://composio.dev/toolkits/moosend/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/moosend/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/moosend/framework/mastra-ai) - [CrewAI](https://composio.dev/toolkits/moosend/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 Moosend - Connect LlamaIndex to the Moosend MCP server - Build a Moosend-powered agent using LlamaIndex - Interact with Moosend 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 Moosend MCP server, and what's possible with it? The Moosend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Moosend account. It provides structured and secure access to your email marketing platform, so your agent can perform actions like managing subscribers, automating campaigns, creating mailing lists, and customizing audience data on your behalf. - Subscriber management and segmentation: Add, update, or search for subscribers in your mailing lists, letting your agent keep your audience organized and up to date. - Campaign creation and analytics: Retrieve, inspect, and manage email campaigns—enabling your agent to help you monitor, review, or even clean up your marketing activities. - Mailing list automation: Create or delete mailing lists as needed, so your agent can reorganize or streamline your audience targeting at scale. - Custom fields and personalization: Build or remove custom fields in your lists, empowering the agent to personalize campaigns and collect richer subscriber data. - Campaign and list cleanup: Direct your agent to permanently remove campaigns or mailing lists you no longer need, keeping your marketing hub tidy and efficient. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `MOOSEND_ADD_SEGMENT_CRITERIA` | Add Segment Criteria | Tool to add a new criterion (rule) to a segment. Use after obtaining the mailing list ID and segment ID to define filtering criteria. | | `MOOSEND_ADD_SUBSCRIBER` | Add or Update Subscriber | Tool to add or update a subscriber in a mailing list. Use after obtaining the mailing list ID to manage subscribers. | | `MOOSEND_CLONE_CAMPAIGN` | Clone Campaign | Tool to clone an existing campaign, creating an exact copy with the same content and settings. Use when you want to reuse a campaign template or create variations of an existing campaign. The cloned campaign is created as a new draft that can be modified independently. | | `MOOSEND_CREATE_CUSTOM_FIELD` | Create custom field | Tool to create a custom field in a mailing list. Use when you need to define a new custom field for subscriber data. | | `MOOSEND_CREATE_MAILING_LIST` | Create Mailing List | Tool to create a new empty mailing list in Moosend. Use after obtaining API key. | | `MOOSEND_CREATE_SEGMENT` | Create Segment | Tool to create a new segment for a mailing list. Use to organize subscribers based on criteria or create empty segments for future use. | | `MOOSEND_DELETE_CAMPAIGN` | Delete Campaign | Permanently deletes a campaign from your Moosend account by its ID. This action removes draft or sent campaigns irreversibly. Use this when you need to clean up campaigns that are no longer needed. The campaign ID can be obtained from listing campaigns or retrieved when a campaign is created. Always verify the campaign ID before deletion as this operation cannot be undone. | | `MOOSEND_DELETE_CUSTOM_FIELD` | Delete custom field | Tool to remove a custom field definition from a mailing list. Use when you have confirmed the custom field ID to delete. | | `MOOSEND_DELETE_MAILING_LIST` | Delete Mailing List | Tool to delete a mailing list. Use when you need to permanently remove a mailing list from your Moosend account after confirming its ID. Deletion is irreversible. | | `MOOSEND_GET_ALL_CAMPAIGNS` | Get all campaigns | Tool to retrieve a list of all campaigns in your account. Use after acquiring valid API credentials to explore campaign data. | | `MOOSEND_GET_ALL_SUBSCRIBERS` | Get All Subscribers | Retrieves all subscribers from a specified mailing list, filtered by their subscription status (Subscribed, Unsubscribed, Bounced, or Removed). Returns paginated results with subscriber details including email, name, custom fields, and subscription timestamps. | | `MOOSEND_GET_CAMPAIGN_DETAILS` | Get Campaign Details | Retrieves comprehensive details about a specific campaign by its ID. Returns complete campaign information including configuration, status, content, and settings. Use this when you need to inspect or verify campaign properties. | | `MOOSEND_GET_CAMPAIGN_STATS_BY_LOCATION` | Get Campaign Stats by Location | Retrieves a detailed report of campaign opens (unique and total) by country. Use this when you need to analyze the geographic distribution of email campaign engagement. | | `MOOSEND_GET_MAILING_LIST_DETAILS` | Get Mailing List Details | Gets details for a given mailing list including name, member counts, status, and custom field definitions. Optionally include subscriber statistics. Use this when you need to inspect mailing list properties or verify list configuration. | | `MOOSEND_GET_SUBSCRIBER_BY_EMAIL` | Get Subscriber By Email | Retrieves detailed subscriber information by email address from a specific mailing list. Returns comprehensive subscriber data including ID, name, subscription status, custom fields, tags, preferences, and timestamps for creation, updates, and unsubscribe events. Use this when you need to: - Look up a subscriber's details using their email address - Check if an email is already subscribed to a list - Retrieve custom field values for a subscriber - Check subscription status and history Example: "Get subscriber details for jane.doe@example.com in list 04fad8e2-..." | | `MOOSEND_LIST_ALL_MAILING_LISTS` | List all mailing lists | Tool to get a list of your active mailing lists in your account. Use after acquiring valid API credentials to explore mailing list data. Optionally include statistics and sort results by various fields. | | `MOOSEND_LIST_ALL_SENDERS` | List all senders | Tool to retrieve a list of all active senders in your account. Use when you need to view available sender email addresses for campaigns. | | `MOOSEND_LIST_CAMPAIGNS_WITH_PAGING` | List campaigns with paging | Tool to retrieve a paginated list of all campaigns in your account with detailed information. Use when you need to fetch campaigns with specific page size and sorting options. Paging information is required as input. | | `MOOSEND_LIST_SEGMENTS` | List Segments | Tool to get a list of all segments with their criteria for a specified mailing list. Use when you need to retrieve segment definitions for targeting specific subscriber groups. | | `MOOSEND_REMOVE_MULTIPLE_SUBSCRIBERS` | Remove Multiple Subscribers | Tool to permanently remove multiple subscribers from a mailing list. Use when you need to delete multiple subscribers permanently without adding them to the suppression list. Invalid email addresses are automatically ignored. | | `MOOSEND_SCHEDULE_CAMPAIGN` | Schedule Campaign | Tool to schedule a campaign. Use when you want to set a specific date and time for campaign delivery after confirming its ID. | | `MOOSEND_SEND_CAMPAIGN` | Send Campaign | Tool to send an existing draft campaign immediately. Use when you want to dispatch a campaign to all recipients after final review. | | `MOOSEND_UNSCHEDULE_CAMPAIGN` | Unschedule Campaign | Tool to unschedule a campaign. Removes a previously defined scheduled date and time from a campaign, so that it will be delivered immediately if already queued or when sent. | | `MOOSEND_UNSUBSCRIBE_FROM_ACCOUNT` | Unsubscribe From Account | Tool to unsubscribe a subscriber from the account. Use when you need to remove a subscriber from all mailing lists. Note: Rate limit is 20 requests per 10 seconds per API key. | | `MOOSEND_UNSUBSCRIBE_FROM_MAILING_LIST` | Unsubscribe from Mailing List | Tool to unsubscribe a subscriber from a specified mailing list. Use when you need to remove a subscriber's active subscription. Rate limit: 20 requests per 10 seconds per API key. | | `MOOSEND_UPDATE_CAMPAIGN` | Update Campaign | Tool to update a draft campaign. Use when you want to modify properties of an existing draft campaign before sending. | | `MOOSEND_UPDATE_CUSTOM_FIELD` | Update custom field | Tool to update properties of an existing custom field in a mailing list. Use after confirming mailing list and custom field IDs. | | `MOOSEND_UPDATE_MAILING_LIST` | Update Mailing List | Tool to update the properties of an existing mailing list. Use when you need to change list metadata after confirming the list ID. | | `MOOSEND_UPDATE_SEGMENT` | Update Segment | Tool to update properties and criteria of an existing segment. Use when you need to modify segment name, match type, or filtering criteria. | | `MOOSEND_UPDATE_SEGMENT_CRITERIA` | Update Segment Criteria | Tool to update an existing criterion in a segment. Use when you need to modify filtering rules for a mailing list segment. | | `MOOSEND_UPDATE_SUBSCRIBER` | Update Subscriber | Tool to update a subscriber in the specified mailing list. Use when you need to modify subscriber information like email, name, or custom fields. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Moosend MCP server is an implementation of the Model Context Protocol that connects your AI agent to Moosend. It provides structured and secure access so your agent can perform Moosend 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 Moosend account and project - Basic familiarity with async Python/Typescript ### 1. Getting API Keys for OpenAI, Composio, and Moosend 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 Moosend 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, moosend) - 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 Moosend 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=["moosend"], ) 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 Moosend actions." system_prompt = """ You are a helpful assistant connected to Composio Tool Router. Use the available tools to answer user queries and perform Moosend 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: ["moosend"], }, ); 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 Moosend 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) { 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 Moosend ```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 Moosend, 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=["moosend"], ) 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 Moosend actions." system_prompt = """ You are a helpful assistant connected to Composio Tool Router. Use the available tools to answer user queries and perform Moosend 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: ["moosend"], }, ); 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 Moosend actions." , llm, tools, }); return agent; } async function chatLoop(agent: ReturnType) { 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 Moosend to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways: - Tool Router dynamically exposes Moosend 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 Moosend MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/moosend/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/moosend/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/moosend/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/moosend/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/moosend/framework/codex) - [OpenClaw](https://composio.dev/toolkits/moosend/framework/openclaw) - [Hermes](https://composio.dev/toolkits/moosend/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/moosend/framework/cli) - [Google ADK](https://composio.dev/toolkits/moosend/framework/google-adk) - [LangChain](https://composio.dev/toolkits/moosend/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/moosend/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/moosend/framework/mastra-ai) - [CrewAI](https://composio.dev/toolkits/moosend/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 Moosend MCP? With a standalone Moosend MCP server, the agents and LLMs can only access a fixed set of Moosend tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Moosend 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 Moosend tools. ### Can I manage the permissions and scopes for Moosend while using Tool Router? Yes, absolutely. You can configure which Moosend 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 Moosend data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)