How to integrate Recallai MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Recallai logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Recallai to Google ADK using the Composio tool router. By the end, you'll have a working Recallai agent that can start recording your zoom meeting now, list all bots active in meetings, retrieve chat messages from today's calls through natural language commands.

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

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

Also integrate Recallai with

TL;DR

Here's what you'll learn:
  • Get a Recallai account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Recallai
  • Build an agent that connects to Recallai through MCP
  • Interact with Recallai 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 Recallai MCP server, and what's possible with it?

The Recallai MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Recallai account. It provides structured and secure access to your meeting bots and conversation data, so your agent can create bots, manage recordings, retrieve chat messages, and orchestrate meeting participation on your behalf.

  • Automated bot creation and management: Quickly spin up new meeting bots, retrieve details, and remove bots as needed for your meetings.
  • Meeting recording control: Let your agent start or stop recordings during live calls, ensuring you capture the most important moments hands-free.
  • Chat message retrieval: Effortlessly access and analyze chat messages exchanged during meetings, enabling summaries or follow-up actions.
  • Bot participation orchestration: Seamlessly remove bots from calls when their job is done, keeping your meetings efficient and secure.
  • Comprehensive bot listing and oversight: View and manage all active bots connected to your Recallai account for smooth operations and tracking.

Supported Tools & Triggers

Tools
Create botCreate a new bot to join and record a meeting.
Create Calendar IntegrationTool to create a new calendar integration with Google Calendar or Microsoft Outlook.
Create Calendar Authentication TokenTool to generate an authentication token for calendar APIs, scoped to the user.
Create Google LoginTool to create a new Google Login credential within a login group.
Create Google Login GroupTool to create a new Google Login Group for managing bot authentication.
Create Meeting Direct ConnectTool to create a Meeting Direct Connect for Google Meet or Zoom.
Create SDK UploadCreate a new Desktop SDK upload.
Create Zoom OAuth AppTool to create a new Zoom OAuth App integration with Recall.
Delete botDelete a scheduled bot by ID.
Delete Bot MediaDeletes bot media stored by Recall AI.
Delete calendarDelete a calendar by ID.
Delete Calendar UserDelete calendar user and disconnect any connected calendars.
Destroy Google LoginTool to delete an existing Google Login by ID.
Destroy Google Login GroupTool to delete an existing Google Login Group by ID.
Destroy Zoom OAuth AppTool to delete a Zoom OAuth App by ID.
Disconnect Calendar UserTool to disconnect a calendar platform (Google or Microsoft) from the user's Recall.
List audio mixedList audio mixed artifacts from Recall.
List Audio SeparateList audio separation artifacts from recordings.
List botsList all bots in your Recall.
List Bot ScreenshotsList all screenshots captured by a bot during a meeting.
List Calendar EventsGet a list of calendar events from connected calendars.
List calendar meetingsList all calendar meetings for the authenticated calendar user.
List calendarsTool to retrieve a list of calendars integrated with Recall.
List calendar usersList all calendar users created for the account.
List chat messagesGet list of chat messages read by the bot in the meeting(excluding messages sent by the bot itself).
List Google Login GroupsTool to retrieve a list of all Google Login Groups in your Recall.
List Google LoginsTool to retrieve a list of all Google Logins in your Recall.
List Meeting Direct ConnectsList all Meeting Direct Connect instances in your Recall.
List Meeting MetadataList meeting metadata from Recall.
List participant eventsList participant events artifacts from recorded meetings.
List Realtime EndpointsTool to list realtime endpoints from Recall.
List RecordingsTool to list recordings from Recall.
List Desktop SDK UploadsTool to get a paginated list of all Desktop SDK uploads in your Recall.
List Slack TeamsTool to list all Slack team integrations.
List transcriptTool to list transcripts from Recall.
List Video Mixed ArtifactsList video mixed artifacts from recorded meetings.
List video separateList video separate artifacts from Recall.
List zoom meetings to credentialsTool to retrieve mappings from Zoom Meeting IDs to Zoom OAuth Credentials.
List Zoom OAuth App LogsTool to retrieve Zoom OAuth app logs from Recall.
List Zoom OAuth AppsTool to retrieve a list of Zoom OAuth apps configured in Recall.
List Zoom OAuth Credential LogsTool to retrieve all Zoom OAuth Credential logs from Recall.
List Zoom OAuth CredentialsTool to retrieve a list of all Zoom OAuth credentials in your Recall.
Remove bot from callRemoves the bot from the meeting call.
Retrieve Billing UsageRetrieve bot usage statistics for billing purposes.
Retrieve botRetrieve detailed information about a specific bot instance by its ID.
Retrieve calendarsRetrieve detailed information about a specific calendar by its UUID.
Retrieve Google Login GroupTool to retrieve an existing Google Login Group by its ID.
Retrieve Meeting Direct ConnectTool to retrieve detailed information about a Meeting Direct Connect instance by its ID.
Retrieve recordingTool to retrieve detailed information about a specific recording by its UUID.
Retrieve sdk uploadRetrieve detailed information about a Desktop SDK upload instance by its ID.
Retrieve Video MixedRetrieve a video mixed artifact by its ID.
Retrieve Zoom OAuth AppRetrieve detailed information about a specific Zoom OAuth app by its ID.
Start recordingInstructs the bot to start recording the meeting.
Stop recordingStops the current recording for the specified bot.
Update BotTool to partially update a scheduled bot.
Update CalendarUpdate an existing calendar integration in Recall.
Update Calendar UserUpdate recording preferences and calendar connections for a calendar user.
Update Google LoginTool to update an existing Google Login credential.
Update Google Login GroupTool to update an existing Google Login Group in Recall.
Partial Update Google Login GroupTool to partially update an existing Google Login Group in Recall.
Update RecordingTool to update a recording's metadata.
Update Video MixedTool to partially update a video mixed artifact by ID.
Update Zoom OAuth AppTool to update an existing Zoom OAuth App's credentials.

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

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

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.

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 Recallai via MCP
  • python-dotenv loads environment variables

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

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

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

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

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

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

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

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 Recallai operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Recallai 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.

How to build Recallai MCP Agent with another framework

FAQ

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

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

Can I use Tool Router MCP with Google ADK?

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

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

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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.