MCP
Overview
Recall.ai provides a managed MCP server for providing read-only access to Recall.ai workspaces, bots, calendars, bot logs, and developer documentation from MCP-compatible AI clients.
How to Set Up
Choose the Recall.ai region that matches your workspace:
| Region | MCP URL |
|---|---|
| US East | https://us-east-1.recall.ai/mcp |
| US West | https://us-west-2.recall.ai/mcp |
| Europe | https://eu-central-1.recall.ai/mcp |
| Asia Pacific | https://ap-northeast-1.recall.ai/mcp |
MCP clients that support remote HTTP MCP can connect directly to the MCP URL and discover authentication from it. Use recall-ai as the MCP server name in each client.
Cursor Example
{
"mcpServers": {
"recall-ai": {
"url": "https://us-east-1.recall.ai/mcp"
}
}
}Windsurf Example
{
"mcpServers": {
"recall-ai": {
"serverUrl": "https://us-east-1.recall.ai/mcp"
}
}
}Claude Desktop Example
In Claude Desktop:
- Open Settings.
- Go to Connectors.
- Add a custom connector.
- Use
recall-aias the connector name. - Use
https://us-east-1.recall.ai/mcpas the connector URL. - Connect and complete the Recall.ai OAuth flow.
Claude Code Example
claude mcp add --transport http recall-ai https://us-east-1.recall.ai/mcpCodex Example
codex mcp add recall-ai --url https://us-east-1.recall.ai/mcpAvailable Tools
The Recall.ai MCP server exposes read-only tools scoped to the workspace selected during authorization. If your account can access multiple workspaces, use list_workspaces to find the workspace ID and pass it as workspace_id to workspace-scoped tools.
| Tool Name | Description | Use Case |
|---|---|---|
get_info | Return the authenticated user, current workspace, organization, and API version. | Confirm which Recall.ai account and workspace the MCP connection is using. |
list_workspaces | List workspaces available to the authenticated account. | Find the workspace ID for follow-up bot, calendar, log, or docs requests. |
list_bots | List bots in a workspace with filters for status, platform, meeting URL, join time, and metadata. | Find recent bots or locate a bot UUID for debugging. |
get_bot | Fetch detailed bot metadata, lifecycle events, participant activity, and chat messages. | Inspect what happened during a specific meeting bot run. |
get_bot_logs | Fetch customer-visible runtime logs for a bot. | Debug join, recording, and meeting behavior. |
list_calendars | List calendars in a workspace, with filters for email, platform, and connection status. | Find a user's connected calendar. |
get_calendar | Fetch one calendar and its connection details. | Inspect a calendar integration's current state. |
list_calendar_events | List calendar events with filters for calendar, iCal UID, deleted state, update time, and start time. | Inspect scheduled meetings and calendar sync behavior. |
get_calendar_event | Fetch one calendar event. | Inspect a specific synced event. |
get_bot_calendar_events | Return calendar events that scheduled a bot. | Connect a bot back to the calendar event that created it. |
list_docs | List Recall.ai guide and API reference pages. | Browse available documentation for the current workspace API version. |
search_docs | Search Recall.ai documentation and API reference pages. | Find relevant docs by endpoint, product term, error text, or concept. |
get_doc | Fetch a Recall.ai documentation page by slug. | Read the full documentation page returned by list_docs or search_docs. |
Examples in Action
Bot Debugging
User: "Why did bot 7d6ac4c3-69ef-49a4-a2d9-06723c0a235a fail to join?"
Assistant: [Uses get_bot and get_bot_logs]
Response: "The bot entered a fatal state after receiving a meeting access error..."
Documentation Search
User: "Find the docs for creating a meeting bot."
Assistant: [Uses search_docs, then get_doc]
Response: "The relevant guide is agent-quickstarts. It explains how to create a bot..."Updated 6 days ago