How to integrate Apollo MCP with LlamaIndex

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Apollo Logo
LlamaIndex Logo
divider

Introduction

This guide walks you through connecting Apollo to LlamaIndex using the Composio tool router. By the end, you'll have a working Apollo agent that can bulk enrich profiles for new leads, add contacts to outreach sequence now, create a new sales deal for acme, list all opportunity stages in pipeline through natural language commands.

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

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

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

The Apollo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Apollo account. It provides structured and secure access to your CRM and lead generation data, so your agent can create contacts, enrich organizations, manage deals, update account stages, and automate tasks for your sales pipeline—all on your behalf.

  • Contact and account creation: Instantly add new contacts or accounts to Apollo, linking them to organizations and stages to keep your CRM up to date with zero manual entry.
  • Bulk data enrichment: Rapidly enrich multiple people or organizations at once, leveraging Apollo's database to fill gaps and update your records with the latest information.
  • Sales opportunity and pipeline management: Let your agent create new deals, retrieve opportunity stages, and move accounts through your sales funnel to optimize pipeline performance.
  • Automated outreach sequencing: Add contacts to email sequences, making it easy to launch targeted campaigns and follow-ups without lifting a finger.
  • Task creation and label organization: Generate actionable Apollo tasks for your team and organize contacts or accounts with labels, so nothing slips through the cracks.

Supported Tools & Triggers

Tools
Add Contacts to SequenceAdds contacts to a specified apollo email sequence by initiating an asynchronous background job and returning its details.
Bulk organization enrichmentEnriches data for up to 10 organizations simultaneously by providing a list of their base company domains (e.
Bulk people enrichmentUse to enrich multiple person profiles simultaneously with comprehensive data from apollo's database.
Bulk update account stageBulk updates the stage for specified existing apollo.
Create an Apollo accountCreates a new account in apollo.
Create Apollo contactCreates a new contact in apollo.
Create Apollo dealCreates a new sales opportunity (deal) in apollo.
Create Apollo TaskCreates a distinct apollo.
Get LabelsRetrieves all labels from apollo.
Get opportunity stagesRetrieves all configured opportunity (deal) stages from the apollo.
Get Organization Job PostingsRetrieves paginated job postings for a specified organization by its id, optionally filtering by domain; ensure `organization id` is a valid identifier.
Get typed custom fieldsRetrieves all typed custom field definitions available in the apollo.
List Apollo account stagesRetrieves all available apollo.
List apollo contact stagesRetrieves all available contact stages from an apollo account, including their unique ids and names.
List Apollo dealsRetrieves a list of deals from apollo, using apollo's default sort order if 'sort by field' is omitted.
List email accountsRetrieves all email accounts and their details for the authenticated user; takes no parameters.
List Apollo UsersRetrieves a list of all users (teammates) associated with the apollo account, supporting pagination via `page` and `per page` parameters.
Enrich organization dataFetches comprehensive organization enrichment data from apollo.
Search organizations in ApolloSearches apollo's database for organizations using various filters; consumes credits (unavailable on free plans), retrieves a maximum of 50,000 records, and uses `page` (1-500) and `per page` (1-100) for pagination.
Enrich person with ApolloEnriches and retrieves information for a person from apollo.
Apollo people searchSearches apollo's contact database for people using various filters; results are limited to 50,000 records and this action does not enrich contact data.
Search Apollo AccountsSearches for accounts within your existing apollo.
Search Apollo contactsSearches apollo contacts using keywords, stage ids (from 'list contact stages' action), or sorting (max 50,000 records; `sort ascending` requires `sort by field`).
Search sequencesSearches for sequences (e.
Search tasksSearches for tasks in apollo.
Update an Apollo accountUpdates specified attributes of an existing account in apollo.
Update Apollo contactUpdates specified attributes of an existing apollo.
Update contact ownershipUpdates the ownership of specified apollo contacts to a given apollo user, who must be part of the same team.
Update contact stageUpdates the stage for one or more existing contacts in apollo.
Update contact status in sequenceUpdates a contact's status within a designated apollo sequence, but cannot set the status to 'active'.
Update Apollo dealUpdates specified fields of an existing apollo.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

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

Getting API Keys for OpenAI, Composio, and Apollo

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

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

  • composio-llamaindex: Composio's LlamaIndex integration
  • llama-index: Core LlamaIndex framework
  • llama-index-llms-openai: OpenAI LLM integration
  • llama-index-tools-mcp: MCP client for LlamaIndex
  • python-dotenv: Environment variable management

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 Apollo access

Import modules

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()

Create a new file called apollo_llamaindex_agent.py and import the required modules:

Key imports:

  • asyncio: For async/await support
  • Composio: Main client for Composio services
  • LlamaIndexProvider: Adapts Composio tools for LlamaIndex
  • ReActAgent: LlamaIndex's reasoning and action agent
  • BasicMCPClient: Connects to MCP endpoints
  • McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

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")

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

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=["apollo"],
    )

    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 Apollo actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Apollo actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

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

Create an interactive chat loop

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}")

What's happening here:

  • We're creating a direct terminal interface to chat with your Apollo database
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

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!")

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 Apollo

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with Apollo and LlamaIndex:

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=["apollo"],
    )

    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 Apollo actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Apollo 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!")

Conclusion

You've successfully connected Apollo to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Apollo 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 Apollo MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Apollo MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Apollo MCP with Claude Agent SDK

Google ADK

Google ADK

Use Apollo MCP with Google ADK

LangChain

LangChain

Use Apollo MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Apollo MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Apollo MCP with Mastra AI

CrewAI

CrewAI

Use Apollo MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Apollo MCP?

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

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

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free