Apollo with LlamaIndex

How to integrate Apollo MCP with LlamaIndex

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Apollo with TL;DR What is LlamaIndex What is the Apollo MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Apollo MCP Agent with another framework Explore Other Toolkits FAQ

Connect Apollo without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

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

Also integrate Apollo with

ChatGPT OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI CrewAI

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 and returns the contact 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.

Bulk create Apollo accountsCreates multiple accounts in Apollo.

Bulk create Apollo contactsTool to bulk create multiple contacts in Apollo with a single API call.

Create call record in ApolloTool to log call records in Apollo from external systems.

Create Apollo contactCreates a new contact in Apollo.

Create custom fieldCreates a new custom field in Apollo.

Create Apollo dealCreates a new sales opportunity (deal) in Apollo.

Create Apollo TaskTool to create a single task in Apollo.

Get Account by IDTool to retrieve detailed information about a specific account by its Apollo ID.

Check Apollo API key statusTool to check whether the provided Apollo API key is valid and accepted by Apollo (health/auth check).

Get Apollo ContactRetrieves detailed information about a specific contact by its ID.

Get Apollo dealRetrieves information about a specific deal by its ID.

Get LabelsRetrieves all labels from Apollo.

Get opportunity stagesRetrieves all configured opportunity (deal) stages from the Apollo.

Get Organization by IDRetrieves complete information about a specific organization by its Apollo ID.

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 the IDs for all available account stages in your team's Apollo account.

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 FieldsRetrieves all field definitions from Apollo.

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 on every call (unavailable on free plans) — avoid re-running identical queries and surface quota errors rather than retrying.

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 capped at 50,000 records and does not enrich contact data.

Search Apollo AccountsSearches for accounts within your existing Apollo.

Search for CallsSearches for call records in 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 news articlesTool to search for news articles about companies in Apollo's database.

Search outreach emailsTool to search for outreach emails sent through Apollo sequences.

Search sequencesSearches for sequences (e.

Search tasksSearches for tasks in Apollo.

Update an Apollo accountUpdates specified attributes of an existing account in Apollo.

Update account ownershipUpdates the ownership of multiple Apollo accounts to a specified user.

Update Apollo call recordTool to update an existing call record in Apollo.

Update Apollo contact detailsTool to update an existing contact's information in Apollo.

Update contact ownershipUpdates the ownership of specified Apollo contacts to a given Apollo user, who must be part of the same team.

Bulk update Apollo contactsTool to bulk update multiple Apollo contacts with a single API call.

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.

View API Usage StatsFetches Apollo API usage statistics and rate limits for the connected team.

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:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
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

ChatGPT

Use Apollo MCP with ChatGPT

OpenAI Agents SDK

Use Apollo MCP with OpenAI Agents SDK

Claude Agent SDK

Use Apollo MCP with Claude Agent SDK

Claude Code

Use Apollo MCP with Claude Code

Claude Cowork

Use Apollo MCP with Claude Cowork

Codex

Use Apollo MCP with Codex

Cursor

Use Apollo MCP with Cursor

OpenClaw

Use Apollo MCP with OpenClaw

Hermes

Use Apollo MCP with Hermes

CLI

Use Apollo MCP with CLI

Google ADK

Use Apollo MCP with Google ADK

LangChain

Use Apollo MCP with LangChain

Vercel AI SDK

Use Apollo MCP with Vercel AI SDK

Mastra AI

Use Apollo MCP with Mastra AI

CrewAI

Use Apollo MCP with CrewAI

OpenCode

Use Apollo MCP with OpenCode

VS Code

Use Apollo MCP with VS Code

Explore Other Toolkits

Hubspot

Oauth2Api Key

HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.

Pipedrive

Oauth2Api Key

Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.

Salesforce

Oauth2S2s Oauth2

Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships.

TOOLKIT MARKETPLACE

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

Never worry about agent reliability

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

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate Apollo MCP with LlamaIndex

Table of Contents

Connect Apollo without Auth hassles

Introduction

Also integrate Apollo with

TL;DR

What is LlamaIndex?

What is the Apollo MCP server, and what's possible with it?

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI, Composio, and Apollo

Installing dependencies

Set environment variables

Import modules

Load environment variables and initialize Composio

Create a Tool Router session and build the agent function

Create an interactive chat loop

Define the main entry point

Run the agent

Complete Code

Conclusion

How to build Apollo MCP Agent with another framework

ChatGPT

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

Cursor

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

CrewAI

OpenCode

VS Code

Explore Other Toolkits

Hubspot

Pipedrive

Salesforce

FAQ

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

Can I use Tool Router MCP with LlamaIndex?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability