How to integrate Recallai MCP with OpenAI Agents SDK

This guide walks you through connecting Recallai to the OpenAI Agents SDK 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 OpenAI Agents SDK 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 freeGet a demo
Recallai logoRecallai
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

Introduction

This guide walks you through connecting Recallai to the OpenAI Agents SDK 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 OpenAI Agents SDK 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

Claude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Recallai
  • Configure an AI agent that can use Recallai as a tool
  • Run a live chat session where you can ask the agent to perform Recallai operations

What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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:

  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 OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Recallai project
  • Some knowledge of Python or Typescript
2

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
3

Install dependencies

npm install @composio/openai-agents @openai/agents dotenv

Install the Composio SDK and the OpenAI Agents SDK.

4

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

5

Import dependencies

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Recallai.
6

Set up the Composio instance

dotenv.config();

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
What's happening:
  • dotenv.config() loads your .env file so COMPOSIO_API_KEY and USER_ID are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.
7

Create a Tool Router session

// Create Tool Router session for Recallai
const session = await composio.create(userId as string, {
  toolkits: ['recallai'],
});
const mcpUrl = session.mcp.url;

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only recallai.
  • The router checks the user's Recallai connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Recallai.
  • This approach keeps things lightweight and lets the agent request Recallai tools only when needed during the conversation.
8

Configure the agent

// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Recallai. Help users perform Recallai operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Recallai and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a hostedMcpTool that connects to the MCP server URL we created earlier.
  • The headers object includes the Composio API key for secure authentication with the MCP server.
  • requireApproval: 'never' means the agent can execute Recallai operations without asking for permission each time, making interactions smoother.
9

Start chat loop and handle conversation

// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

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

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

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

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

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

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
What's happening:
  • The program prints a session URL that you visit to authorize Recallai.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using run().
  • The responses are printed to the console.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Recallai and OpenAI Agents SDK:

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['recallai'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Recallai. Help users perform Recallai operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

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

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

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

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

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

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\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

This was a starter code for integrating Recallai MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Recallai.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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

Claude Agent SDK logo

Claude Agent SDK

Use Recallai MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Recallai MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Recallai MCP with Claude Cowork

Codex logo

Codex

Use Recallai MCP with Codex

OpenClaw logo

OpenClaw

Use Recallai MCP with OpenClaw

Hermes logo

Hermes

Use Recallai MCP with Hermes

CLI logo

CLI

Use Recallai MCP with CLI

Google ADK logo

Google ADK

Use Recallai MCP with Google ADK

LangChain logo

LangChain

Use Recallai MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Recallai MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Recallai MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Recallai MCP with LlamaIndex

CrewAI logo

CrewAI

Use Recallai MCP with CrewAI

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. OpenAI Agents 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 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 FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

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
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
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
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
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
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
Jerome Leclanche
Co-Founder, Ingram Technologies