How to integrate Aircall MCP with Claude Agent SDK

This guide walks you through connecting Aircall to the Claude Agent SDK 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 Claude Agent SDK 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 the Claude Agent SDK 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 Claude Agent SDK 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:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Aircall
  • Configure an AI agent that can use Aircall as a tool
  • Run a live chat session where you can ask the agent to perform Aircall operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Aircall account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Aircall functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

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

  // Create Tool Router session for Aircall
  const session = await composio.create(USER_ID, {
    toolkits: ['aircall'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Aircall
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Aircall tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Aircall
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Aircall and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['aircall']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Aircall tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Aircall through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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. Claude Agent SDK 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