How to integrate Aircall MCP with LlamaIndex

This guide walks you through connecting Aircall to LlamaIndex using the Composio tool router. By the end, you'll have a working Aircall agent that can manage calls, search contacts, update teams, organize phone numbers, and apply tags through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Aircall account through Composio's Aircall MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Aircall logoAircall
Oauth2Basic

Aircall is a cloud-based phone and call-center platform for business communications. It centralizes calls, contacts, teams, numbers, and tags in one place.

48 Tools

Introduction

This guide walks you through connecting Aircall to LlamaIndex using the Composio tool router. By the end, you'll have a working Aircall agent that can manage calls, search contacts, update teams, organize phone numbers, and apply tags through natural language commands.

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

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

Also integrate Aircall with

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

The Aircall MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Aircall account. It provides structured and secure access to your Aircall calls, users, teams, phone numbers, contacts, tags, and webhooks, so your agent can place calls, search call activity, manage contacts and teams, check user availability, and control call features on your behalf.

  • Call handling and insight: Have your agent place outbound calls, find calls by direction, user, phone number, tags, or date, add comments, manage recording during ongoing calls, delete call audio, and publish insight cards for call agents.
  • Contact management: Let the agent search, create, view, and delete shared contacts, then add or remove their phone numbers and email addresses.
  • User and team administration: Direct your agent to list, create, view, and delete users, create or remove teams, change team membership, and check user availability.
  • Phone numbers and tags: Instruct your agent to list and inspect Aircall phone numbers, check registration status, and create, view, list, or delete call tags.
  • Webhook management: Have your agent create, list, inspect, or delete Aircall webhooks for connected HTTPS destinations.

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

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Aircall account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Aircall

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

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

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Aircall access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called aircall_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

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

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["aircall"],
    },
  );

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

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, aircall)
  • 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 Aircall tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Aircall
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Aircall tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

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

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Aircall
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["aircall"],
    },
  );

  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 Aircall 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 Aircall to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Aircall tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Aircall action and event your agent gets out of the box.

Add Contact Method

Add a phone number or an email address to an existing Aircall contact.

Add User to Team

Add a User to a Team (membership change).

Add Comment to Call

Add a comment/note to a Call (max 5 comments per call; emojis are stripped).

Create Contact

Create a shared Aircall contact.

Create Tag

Create a Tag.

Create Team

Create a new Team.

Create User

Create an Aircall user and send them a real invitation email, consuming a licensed seat.

Create Webhook

Create an Aircall webhook targeting a public HTTPS URL.

Delete Call Media

Request permanent deletion of a Call's audio recording or voicemail, for compliance or data governance.

Delete Contact

Permanently delete a shared Contact and all of its phone numbers and email addresses.

Delete Contact Method

Permanently remove one phone number or email address from an Aircall contact.

Delete Tag

Delete a Tag by id.

Delete Team

Delete a Team by id.

Delete User

Permanently delete a User.

Delete Webhook

Permanently delete an Aircall webhook.

Get Call

Retrieve a single Call by id, with optional contact / short-url / timeline enrichment via the fetch_* flags.

Get Company

Retrieve information about the connected Aircall company (name, users_count, numbers_count).

Get Contact

Retrieve a single shared Contact by id, with its nested phone_numbers[] and emails[].

Get Number

Retrieve a single Aircall phone Number by its numeric id.

Get Number Registration Status

Check whether an Aircall phone number is registered for compliance (10DLC or other regulatory registration) by reading the `status` field.

Get Tag

Retrieve a single Tag by id.

Get Team

Retrieve a single Team by id, including its member users.

Get User

Retrieve one Aircall user by numeric id or by email address.

Get User Availability

Check the current availability of one User.

Get Webhook

Retrieve one Aircall webhook by its UUID or legacy numeric id.

List Calls

List the account's calls in chronological order, covering about 6 months of history and at most 10,000 items via pagination.

List Contacts

List all shared Contacts (hard-capped at 10,000 items via pagination — window past with the `from` timestamp).

List Numbers

List all Aircall phone Numbers in the account.

List Tags

List all Tags in the account.

List Teams

List all Teams in the account.

List User Numbers (V2)

List all Aircall Numbers assigned to a specific User (V2, paginated).

List Users

List the users in the Aircall account, one page at a time with a next_cursor to continue.

List Users Availability

List the detailed availability of all Users (whether each user is available/offline/on a call, etc.

List Webhooks

List webhook subscriptions accessible to the connected Aircall company.

Publish Call Insight Card

Display contextual title, short text, links, or Aircall user details to the agent handling an ongoing call.

Remove User from Team

Remove a User from a Team (membership change).

Search Calls

Find calls matching any combination of direction (inbound or outbound), user_id, phone_number and tag ids, optionally narrowed to a from/to date window.

Search Contacts

Search shared Contacts by phone_number and/or email (optionally within a from/to date window).

Set Call Recording State

Pause or resume recording on an ongoing Aircall call.

Start Outbound Call

Place a real, billable outbound phone call from an Aircall user's desktop Workspace to an external number.

Tag Call

Tag a Call with one or more existing Tag ids (create tags first with AIRCALL_CREATE_TAG).

Transfer Call

Cold-transfer a call that is live right now to one user, one team, or one external phone number.

Update Contact

Update a Contact's core fields (first_name, last_name, company_name, information).

Update Contact Method

Update one phone number or email address that is already on an Aircall contact.

Update Number

Update at least one mutable Number field: name changes its display name; availability_status changes the first Time Rule widget and can open or close call routing; live_recording_activated enables or disables inbound and outbound recording, and audio missed while disabled cannot be recovered; priority changes routing priority; messages replaces or clears supplied Music & Messages audio slots heard by live callers.

Update Tag

Update a Tag (PUT, full replace).

Update User

Update an existing Aircall user's name, availability_status, substatus, roles or wrap-up time in place.

Update Webhook

Update an Aircall webhook's URL, name, active state, or event subscriptions.

FAQ

Frequently asked questions

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

Yes, you can. LlamaIndex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Aircall tools.

Yes, absolutely. You can configure which Aircall scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Aircall data and credentials are handled as safely as possible.

Start with Aircall.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Aircall tool your agent needs.Free to start.

Start building