← All integrations

Recall.ai MCP server

111 operations0 webhooks

Meeting bots, recordings and transcripts with Recall.ai - send bots to Zoom, Google Meet, Teams and Webex calls, control them in the call, read recordings, transcripts and media, schedule bots from calendars, and manage Google logins and Zoom OAuth credentials.

Use Recall.ai in Claude, ChatGPT, Cursor or another MCP client

Connect Recall.ai once in Corsair, then add one MCP address to your agent.

Connect Recall.ai
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Recall.ai with your agent

Connect Recall.ai, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Recall.ai on my account, then run one read-only example and show me the result.

Runs once, when you ask

Recall.ai tools and triggers

Tools are what your agent can do in Recall.ai through Corsair's MCP server. Triggers are the Recall.ai events a routine can start from.

Bot Actions

  • Delete Bot MediaDestructive

    Delete stored media for a Recall.ai bot

    botActions.deleteBotMedia

  • Leave Bot CallDestructive

    Remove a Recall.ai bot from its meeting

    botActions.leaveBotCall

  • Output AudioWrite

    Output audio from a Recall.ai bot

    botActions.outputAudio

  • Output MediaWrite

    Start media output from a Recall.ai bot

    botActions.outputMedia

  • Output VideoWrite

    Output video from a Recall.ai bot

    botActions.outputVideo

  • Pause RecordingWrite

    Pause a Recall.ai bot recording

    botActions.pauseRecording

  • Pin ParticipantWrite

    Pin a participant for a Recall.ai bot

    botActions.pinParticipant

  • Resume RecordingWrite

    Resume a Recall.ai bot recording

    botActions.resumeRecording

  • Send Chat MessageWrite

    Send a chat message from a Recall.ai bot

    botActions.sendChatMessage

  • Start RecordingWrite

    Start a Recall.ai bot recording

    botActions.startRecording

  • Start ScreenshareWrite

    Start bot screenshare in Recall.ai

    botActions.startScreenshare

  • Stop Output AudioWrite

    Stop bot audio output in Recall.ai

    botActions.stopOutputAudio

Connect Recall.ai to Claude, ChatGPT or Cursor

  1. 1

    Connect Recall.ai in Corsair

    Add your Recall.ai API key once in Corsair. Corsair stores the credential encrypted and makes the Recall.ai API calls for your agent, so it never goes into a prompt or a config file. Connect Recall.ai

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Recall.ai. On a ChatGPT personal plan, connect Recall.ai here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Recall.ai's read and write operations run right away and its 19 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/recallai, add the Recall.ai plugin, and connect with an API key. Then call methods like corsair.recallai.api.audioMixed.delete() from your app. Corsair keeps each tenant isolated.

Yes. Recall.ai requires an API key from your Recall.ai account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Recall.ai, GitHub, Notion, Stripe, and the rest. Trigger Recall.ai from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for meeting bots, recordings and transcripts with recall.ai - send bots to zoom, google meet, teams and webex calls, control them in the call, read recordings, transcripts and media, schedule bots from calendars, and manage google logins and zoom oauth credentials. Common builds include sync jobs, admin tooling, and agents that call Recall.ai APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Recall.ai API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/recallai in the open repo. When Recall.ai ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Recall.ai data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Recall.ai data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Recall.ai on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 19 destructive Recall.ai operations. You can change a link's mode at hub.corsair.dev/me.