How to integrate Recallai MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Recallai logo
Claude Code logo
divider

Introduction

Manage your Recallai directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Recallai with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Recallai to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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

Connecting Recallai via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Recallai) for even more tool search precision. It's secure and reliable.

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:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Recallai account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["recallai"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http recallai-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Recallai. This URL will be used to connect Claude Code to Recallai.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Recallai
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Recallai MCP to Claude Code

bash
claude mcp add --transport http recallai-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (recallai-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Recallai MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your recallai-composio entry in the list
  • This confirms that Claude Code can now access Recallai tools

If everything is wired up, you should see your recallai-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Recallai

The first time you try to use Recallai tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Recallai
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Recallai authorization flow
  • Return to the terminal and start using Recallai through Claude Code

Once authenticated, you can ask Claude Code to perform Recallai operations in natural language. For example:

  • "Start recording my Zoom meeting now"
  • "List all bots active in meetings"
  • "Retrieve chat messages from today's calls"

Complete Code

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

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["recallai"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http recallai-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Recallai with Claude Code using Composio's MCP server. Now you can interact with Recallai directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Recallai operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Recallai operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Recallai MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Recallai MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Recallai MCP with Claude Agent SDK

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

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 Claude Code?

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

Get started for freeGet a demo↗