How to integrate Recallai MCP with LangChain

This guide walks you through connecting Recallai to LangChain 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 LangChain 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.

Get started for free Get a demo

Recallai

Api Key

Recallai is the universal API for meeting bots and conversation data. It centralizes call recordings, transcripts, and smart summaries for seamless workflow automation.

63 Tools

Managed auth

Connect Recallai without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your LangChain 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

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your OpenAI and Composio API keys
Connect your Recallai project to Composio
Create a Tool Router MCP session for Recallai
Initialize an MCP client and retrieve Recallai tools
Build a LangChain agent that can interact with Recallai
Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

Agent Framework: Build agents that can use tools and make decisions
MCP Integration: Connect to external services through Model Context Protocol adapters
Memory Management: Maintain conversation history across interactions
Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

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:

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

Step-by-step Guide

Step by step10 STEPS

Prerequisites

Before starting this tutorial, make sure you have:

Python 3.10 or higher installed on your system
A Composio account with an API key
An OpenAI 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

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

@composio/langchain provides Composio integration for LangChain
@langchain/mcp-adapters enables MCP client connections
@langchain/core is the core agent framework
dotenv/config loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates your requests to Composio's API
COMPOSIO_USER_ID identifies the user for session management
OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();

What's happening:

We're importing LangChain's MCP adapter and Composio SDK
The dotenv/config import loads environment variables from your .env file
This setup prepares the foundation for connecting LangChain with Recallai functionality through MCP

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

What's happening:

We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
Creating a Composio instance that will manage our connection to Recallai tools
Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['recallai']
    }
);

const url = session.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
This approach allows the agent to dynamically load and use Recallai tools as needed

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "recallai-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });

What's happening:

We're creating a MultiServerMCPClient that connects to our Recallai MCP server via HTTP
The client is configured with a name and the URL from our Tool Router session
getTools() retrieves all available Recallai tools that the agent can use
We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Recallai related question or task to the agent.\n");

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

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });

What's happening:

We initialize an empty conversationHistory list to maintain context across interactions
A readline interface is used to continuously accept user input from the command line
When a user types a message, it's added to the conversation history and sent to the agent
The agent processes the request using the invoke() method with the full conversation history
Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

What's happening:

We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['recallai']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "recallai-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Recallai related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Recallai through Composio's Tool Router.

Key features of this implementation:

Dynamic tool loading through Composio's Tool Router
Conversation history maintenance for context-aware responses
Async Python provides clean, efficient execution of agent workflows

You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

TOOLS

Supported Tools

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

Create bot

Create a new bot to join and record a meeting.

Create Calendar Integration

Tool to create a new calendar integration with Google Calendar or Microsoft Outlook.

Create Calendar Authentication Token

Tool to generate an authentication token for calendar APIs, scoped to the user.

Create Google Login

Tool to create a new Google Login credential within a login group.

Create Google Login Group

Tool to create a new Google Login Group for managing bot authentication.

Create Meeting Direct Connect

Tool to create a Meeting Direct Connect for Google Meet or Zoom.

Create SDK Upload

Create a new Desktop SDK upload.

Create Zoom OAuth App

Tool to create a new Zoom OAuth App integration with Recall.

Delete bot

Delete a scheduled bot by ID.

Delete Bot Media

Deletes bot media stored by Recall AI.

Delete calendar

Delete a calendar by ID.

Delete Calendar User

Delete calendar user and disconnect any connected calendars.

Destroy Google Login

Tool to delete an existing Google Login by ID.

Destroy Google Login Group

Tool to delete an existing Google Login Group by ID.

Destroy Zoom OAuth App

Tool to delete a Zoom OAuth App by ID.

Disconnect Calendar User

Tool to disconnect a calendar platform (Google or Microsoft) from the user's Recall.

List audio mixed

List audio mixed artifacts from Recall.

List Audio Separate

List audio separation artifacts from recordings.

List bots

List all bots in your Recall.

List Bot Screenshots

List all screenshots captured by a bot during a meeting.

List Calendar Events

Get a list of calendar events from connected calendars.

List calendar meetings

List all calendar meetings for the authenticated calendar user.

List calendars

Tool to retrieve a list of calendars integrated with Recall.

List calendar users

List all calendar users created for the account.

List chat messages

Get list of chat messages read by the bot in the meeting(excluding messages sent by the bot itself).

List Google Login Groups

Tool to retrieve a list of all Google Login Groups in your Recall.

List Google Logins

Tool to retrieve a list of all Google Logins in your Recall.

List Meeting Direct Connects

List all Meeting Direct Connect instances in your Recall.

List Meeting Metadata

List meeting metadata from Recall.

List participant events

List participant events artifacts from recorded meetings.

List Realtime Endpoints

Tool to list realtime endpoints from Recall.

List Recordings

Tool to list recordings from Recall.

List Desktop SDK Uploads

Tool to get a paginated list of all Desktop SDK uploads in your Recall.

List Slack Teams

Tool to list all Slack team integrations.

List transcript

Tool to list transcripts from Recall.

List Video Mixed Artifacts

List video mixed artifacts from recorded meetings.

List video separate

List video separate artifacts from Recall.

List zoom meetings to credentials

Tool to retrieve mappings from Zoom Meeting IDs to Zoom OAuth Credentials.

List Zoom OAuth App Logs

Tool to retrieve Zoom OAuth app logs from Recall.

List Zoom OAuth Apps

Tool to retrieve a list of Zoom OAuth apps configured in Recall.

List Zoom OAuth Credential Logs

Tool to retrieve all Zoom OAuth Credential logs from Recall.

List Zoom OAuth Credentials

Tool to retrieve a list of all Zoom OAuth credentials in your Recall.

Remove bot from call

Removes the bot from the meeting call.

Retrieve Billing Usage

Retrieve bot usage statistics for billing purposes.

Retrieve bot

Retrieve detailed information about a specific bot instance by its ID.

Retrieve calendars

Retrieve detailed information about a specific calendar by its UUID.

Retrieve Google Login Group

Tool to retrieve an existing Google Login Group by its ID.

Retrieve Meeting Direct Connect

Tool to retrieve detailed information about a Meeting Direct Connect instance by its ID.

Retrieve recording

Tool to retrieve detailed information about a specific recording by its UUID.

Retrieve sdk upload

Retrieve detailed information about a Desktop SDK upload instance by its ID.

Retrieve Video Mixed

Retrieve a video mixed artifact by its ID.

Retrieve Zoom OAuth App

Retrieve detailed information about a specific Zoom OAuth app by its ID.

Start recording

Instructs the bot to start recording the meeting.

Stop recording

Stops the current recording for the specified bot.

Update Bot

Tool to partially update a scheduled bot.

Update Calendar

Update an existing calendar integration in Recall.

Update Calendar User

Update recording preferences and calendar connections for a calendar user.

Update Google Login

Tool to update an existing Google Login credential.

Update Google Login Group

Tool to update an existing Google Login Group in Recall.

Partial Update Google Login Group

Tool to partially update an existing Google Login Group in Recall.

Update Recording

Tool to update a recording's metadata.

Update Video Mixed

Tool to partially update a video mixed artifact by ID.

Update Zoom OAuth App

Tool to update an existing Zoom OAuth App's credentials.

FRAMEWORKS

How to build Recallai MCP Agent with another framework

OpenAI Agents SDK

Use Recallai MCP with OpenAI Agents SDK

Claude Agent SDK

Use Recallai MCP with Claude Agent SDK

Claude Code

Use Recallai MCP with Claude Code

Claude Cowork

Use Recallai MCP with Claude Cowork

Codex

Use Recallai MCP with Codex

OpenClaw

Use Recallai MCP with OpenClaw

Hermes

Use Recallai MCP with Hermes

CLI

Use Recallai MCP with CLI

Google ADK

Use Recallai MCP with Google ADK

Vercel AI SDK

Use Recallai MCP with Vercel AI SDK

Mastra AI

Use Recallai MCP with Mastra AI

LlamaIndex

Use Recallai MCP with LlamaIndex

CrewAI

Use Recallai MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Gmail

Oauth2

Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.

Outlook

Oauth2S2s Oauth2

Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.

Slack

Oauth2

Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.

Gong

BasicOauth2

Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Recallai.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Recallai MCP with LangChain

Connect Recallai without auth hassles

Introduction

Also integrate Recallai with

TL;DR

What is LangChain?

What is the Recallai MCP server, and what's possible with it?

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Initialize Composio client

Create a Tool Router session

Configure the agent with the MCP URL

Set up interactive chat interface

Run the application

Complete Code

Conclusion

Supported Tools

How to build Recallai MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Gmail

Outlook

Slack

Gong

Frequently asked questions

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

Can I use Tool Router MCP with LangChain?+

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

How safe is my data with Composio Tool Router?+

Start with Recallai.It takes 30 seconds.

Teams ship real agents on Composio