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 | Shows the current Recall.ai account, workspace, organization, and API version. | Confirm a support answer targets the correct workspace. |
list_workspaces | Lists Recall.ai workspaces available to the authenticated account. | Locate the workspace behind a customer org name. |
get_service_status | Shows current customer-visible Recall.ai service status. | Confirm whether Teams bots are currently degraded. |
list_service_incidents | Lists historical customer-visible Recall.ai status incidents. | Explain failures during yesterday's Google Meet outage. |
list_rate_limits | Lists configured public API rate limits for a workspace. | Confirm the limit causing repeated 429 responses. |
list_webhook_endpoints | Lists webhook destinations and subscribed event types. | Confirm bot.done is subscribed before tracing webhooks. |
list_webhook_deliveries | Lists webhook events and delivery attempts for a resource. | Trace why a recording.done webhook never arrived. |
list_bots | Lists meeting bots by status, platform, schedule, and metadata. | Locate a bot by meeting URL or app metadata. |
get_bot | Shows bot metadata, lifecycle events, participants, and chat. | Explain waiting-room, participant, and chat evidence. |
list_recordings | Lists recordings by bot, upload, status, time, and metadata. | Find the recording created by a Desktop SDK upload. |
list_audio_mixed | Lists generated mixed-audio artifacts for recordings. | Locate the finished MP3 for a recording. |
get_recording_resource | Fetch recording or transcript artifact details by ID. | Investigate a missing transcript or media artifact. |
list_calendars | Lists calendars in a workspace, with filters for email, platform, and connection status. | Confirm whether a user's calendar is connected. |
get_calendar | Shows details and connection status for one calendar integration. | Explain why one calendar stopped scheduling bots. |
list_calendar_events | Lists synced calendar events by schedule, update time, and deleted state. | Locate synced events in a disputed time window. |
get_calendar_event | Shows details for a single synced calendar event. | Explain why one event did not schedule a bot. |
get_bot_calendar_events | Shows calendar events that scheduled a bot. | Trace a scheduled bot back to its calendar event. |
get_bot_logs | Fetch customer-visible runtime logs for a bot. | Explain why a bot failed to join or record. |
get_workspace_logs | Fetches customer-visible logs for workspace-level activity. | Trace 429 responses on a specific API endpoint. |
list_docs | Lists Recall.ai documentation and API reference pages. | Find the slug for a product guide. |
search_docs | Searches Recall.ai documentation and API reference pages. | Find docs for a specific endpoint or error. |
get_doc | Fetches a full Recall.ai documentation page. | Read the transcription guide by known slug. |
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 1 day ago