Recall.ai for AI agents
Recall.ai gives a unified API for meeting bots and conversation data across major video conferencing platforms. Developers use it to build transcription and meeting analysis features. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Recall.ai.
Create a meeting bot
Send a bot to join a scheduled meeting so it can record and transcribe automatically.
Check bot recordings read-only
List a bot's recorded media to confirm the meeting was captured correctly.
Delete bot media with approval
Remove a recorded meeting's media only after confirming it has been archived elsewhere.
63 Recall.ai actions, graded by risk.
Every Recall.ai action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
35Look things up. Allowed by default.
- recall_ai.list_botsList bots
- recall_ai.list_calendarsList calendars
- recall_ai.list_recordingList Recordings
- recall_ai.list_transcriptList transcript
- recall_ai.list_audio_mixedList audio mixed
- recall_ai.list_sdk_uploadsList Desktop SDK Uploads
- recall_ai.list_slack_teamsList Slack Teams
- recall_ai.list_video_mixedList Video Mixed Artifacts
- recall_ai.list_chat_messagesList chat messages
- recall_ai.list_google_loginsList Google Logins
- recall_ai.list_audio_separateList Audio Separate
- recall_ai.list_calendar_usersList calendar users
- recall_ai.list_video_separateList video separate
- recall_ai.list_bot_screenshotsList Bot Screenshots
- recall_ai.list_calendar_eventsList Calendar Events
- recall_ai.list_zoom_oauth_appsList Zoom OAuth Apps
write
20Create and change things. Allow, or ask the user first.
- recall_ai.create_botCreate bot
- recall_ai.update_botUpdate Bot
- recall_ai.create_calendarCreate Calendar Integration
- recall_ai.update_calendarUpdate Calendar
- recall_ai.update_recordingUpdate Recording
- recall_ai.create_sdk_uploadCreate SDK Upload
- recall_ai.update_video_mixedUpdate Video Mixed
- recall_ai.create_google_loginCreate Google Login
- recall_ai.update_google_loginUpdate Google Login
- recall_ai.update_calendar_userUpdate Calendar User
- recall_ai.create_zoom_oauth_appCreate Zoom OAuth App
- recall_ai.update_zoom_o_auth_appUpdate Zoom OAuth App
- recall_ai.create_google_login_groupCreate Google Login Group
- recall_ai.update_google_login_groupUpdate Google Login Group
- recall_ai.update_google_login_groupsPartial Update Google Login Group
- recall_ai.create_calendar_authenticateCreate Calendar Authentication Token
destructive
8Delete, cancel or archive. Ask first, or deny outright.
- recall_ai.delete_botDelete bot
- recall_ai.delete_calendarDelete calendar
- recall_ai.delete_bot_mediaDelete Bot Media
- recall_ai.remove_bot_from_callRemove bot from call
- recall_ai.destroy_google_loginDestroy Google Login
- recall_ai.destroy_calendar_userDelete Calendar User
- recall_ai.destroy_zoom_o_auth_appDestroy Zoom OAuth App
- recall_ai.destroy_google_login_groupDestroy Google Login Group
Recall.ai in three steps.
- 01Your users connect Recall.aiThey add their Recall.ai api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create bot” can wait for the user, and “delete bot” can be denied outright.
- 03Any agent can actYour agent calls Recall.ai through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('recall_ai', { read: 'allow', write: 'ask', // create_bot destructive: 'deny', // delete_bot }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Recall.ai connects.
Users add their Recall.ai api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Recall.ai connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Recall.ai from any agent.
Recall.ai and Arc0, answered.
Can I use Recall.ai with Claude, ChatGPT or Cursor?
Yes. Connect Recall.ai to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Recall.ai actions you allow.
How do users connect Recall.ai?
Users add their Recall.ai api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Recall.ai actions can my agent take?
63 in total: 35 read, 20 write and 8 destructive, such as “create bot”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Recall.ai?
Yes. Actions like “delete bot” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Recall.ai too?
Yes. The same Recall.ai connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Recall.ai into your agent.
Your users connect Recall.ai once, under your brand. Your agent gets 63 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan