How to integrate Recallai MCP with Pydantic AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Recallai logo
Pydantic AI logo
divider

Introduction

This guide walks you through connecting Recallai to Pydantic AI 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 Pydantic AI 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:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Recallai
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Recallai workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

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:
  • Python 3.9 or higher
  • A Composio account with an active API key
  • Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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.

Install dependencies

bash
pip install composio pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Recallai
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Recallai
  • MCPServerStreamableHTTP connects to the Recallai MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Recallai
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["recallai"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
What's happening:
  • We're creating a Tool Router session that gives your agent access to Recallai tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
recallai_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[recallai_mcp],
    instructions=(
        "You are a Recallai assistant. Use Recallai tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Recallai endpoint
  • The agent uses GPT-5 to interpret user commands and perform Recallai operations
  • The instructions field defines the agent's role and behavior

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Recallai.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Recallai API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with Recallai and Pydantic AI:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Recallai
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["recallai"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    recallai_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[recallai_mcp],
        instructions=(
            "You are a Recallai assistant. Use Recallai tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Recallai.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've built a Pydantic AI agent that can interact with Recallai through Composio's Tool Router. With this setup, your agent can perform real Recallai actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Recallai for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.

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 Pydantic AI?

Yes, you can. Pydantic AI 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.