How to integrate Aircall MCP with Google ADK

This guide walks you through connecting Aircall to Google ADK 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 Google ADK 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 Google ADK 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 Google ADK 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 a Aircall account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Aircall
  • Build an agent that connects to Aircall through MCP
  • Interact with Aircall using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Aircall via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["aircall"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Aircall operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

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

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["aircall"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Aircall operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Aircall with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Aircall using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Aircall tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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