Send a Meeting Bot From Claude and Read Transcripts (2026)

You are about to join a call in a language you only half follow, and the link is sitting in your calendar. What you would like to say to your assistant is simply: join this meeting, translate it for me, and tell me what was agreed afterwards.

That now works. Whisperr connects to Claude through MCP, the open standard that lets an AI assistant use outside tools. Once connected, Claude can send a Whisperr meeting bot into a Zoom, Microsoft Teams or Google Meet call, check on it, stop it, and read back the transcript and its translations when the call is over.

This guide shows the setup in Claude Desktop and in Claude Code, with every screen, and what to ask once it is running.

What Claude can do once Whisperr is connected

Claude gets six Whisperr tools. You never have to name them. You just ask, and Claude picks the right one.

Send a meeting bot to a Zoom, Teams or Google Meet link, with the two languages you want. You get back a live transcript link you can open or share. Anyone who has that link can follow the live captions, so share it only with people you want to include.
Check a bot to see whether it is waiting in the lobby, in the meeting, or has left, and whether the transcript was saved.
Stop a bot so it leaves the meeting.
List your bots to see recent and running ones.
List your conversations to find saved meetings, calls and live sessions from any Whisperr app.
Read a transcript with its translations, so Claude can summarize it, pull out action items, or answer questions about what was said.

Claude does the reading, so you can ask for the result in any language, not only the two the meeting used. A meeting held in Japanese and English can come back as a Spanish recap.

What you need before you start

A Whisperr account. Reading saved conversations works on any account. Sending a bot needs an active Whisperr subscription, and a subscription runs one bot at a time.
Claude Desktop, or Claude Code installed in your terminal. Custom connectors are available on Claude's Free (one connector), Pro and Max plans, and on Team and Enterprise an organization owner adds the connector first. Plans change, so check Anthropic's help pages for what yours includes.
A meeting link for Zoom, Microsoft Teams or Google Meet.

Connect Whisperr to Claude Desktop

Claude Desktop connects to Whisperr as a custom connector. You paste one address, sign in to Whisperr with your normal account, and click Allow. There is no key to copy and nothing to type in a terminal. It takes about two minutes.

Step 1: Copy the connector address from MCP Integration

Sign in to the Whisperr web app and click MCP Integration in the left menu, just below Dictionary. Under Claude on claude.ai or the desktop app, click the copy button next to the address. It ends in /mcp. Keep it on your clipboard for step 4.

Step 2: Open Customize, then Connectors

In Claude Desktop, click Customize in the left sidebar, then open the Connectors tab.

Step 3: Add a custom connector

Click Add at the top right, then choose Add custom connector.

Step 4: Enter a name and the address

Type Whisperr in the first box. In the second box, paste the connector address you copied. Click Continue.

Claude checks the address and recognizes that Whisperr uses sign-in. You will see Sign in now marked Detected, and Register automatically marked Detected under OAuth client. Leave both as they are, leave Request headers empty, and click Add.

Step 6: Click Connect, then continue in your browser

Whisperr now appears in your connectors but says you are not connected yet. Click Connect.

Your browser opens on a Claude page asking Finish connecting a connector? You just started this from Claude Desktop yourself, so click Continue connecting. If you did not start it, click Not now: a link someone sends you can never connect anything on its own.

If you are not signed in, sign in to Whisperr first with Google, Apple or your email. Then you see Connect Claude to Whisperr, with the account you are signed in as and exactly what Claude will be able to do: send Whisperr meeting bots into your Zoom, Teams and Google Meet calls, check and stop your meeting bots, and read your saved conversations and transcripts. Click Allow.

Cancel connects nothing. If it is the wrong account, click Not you? Use a different account.

Step 8: Go back to Claude Desktop

The browser shows Connected and may ask Open Claude? Click Open Claude, then close the tab. Whisperr is now connected.

To use it, open a chat, click the + button at the lower left, choose Connectors, and switch Whisperr on for that conversation. Claude asks before it uses a Whisperr tool. Click Allow each time, or Allow always if you trust it to send bots without asking.

Connect Whisperr to Claude Code (terminal)

Claude Code uses a command. Whisperr makes the command for you, with your own key already inside it.

Step 1: Open MCP Integration in the Whisperr web app

Sign in to the Whisperr web app and click MCP Integration in the left menu, just below Dictionary. The first time you open it, Whisperr creates a key named MCP for you and shows it once, inside a ready-made command.

Step 2: Copy the command and run it

Click the copy button and paste the command into your terminal. It looks like this, with your own address and key in place of the placeholders:

```bash
claude mcp add --scope user --transport http whisperr <server-address>/mcp --header "Authorization: Bearer <your-key>"
```

The --scope user part makes Whisperr available in every folder, not just the one you ran the command in.

Step 3: Check the connection

Run this to see that Whisperr is listed as connected:

```bash
claude mcp list
```

Then start Claude Code with claude and type /mcp. You should see Whisperr with its six tools. If it does not show as connected straight away, wait a few seconds and check again.

Step 4: If Whisperr was already added before

Claude Code refuses to add a server name that already exists. If you connected earlier, or you regenerated your key, remove the old entry first and then run the new command:

```bash
claude mcp remove --scope user whisperr
```

The key is shown only when it is created. If you lose the command, press Regenerate key on the MCP Integration page. The old key stops working, so run the remove command and then the new add command.

Three things to ask Claude

Send a bot to a meeting

Send a Whisperr bot to this Zoom meeting for English and Spanish: (paste the link)

Claude sends the bot and answers with its status and a live transcript link. You pick just two languages. Translation runs both ways by default, so whoever speaks, you can follow along. It works as a realtime voice translator for the call: live voice translation captions in the language you read best, plus a saved transcript afterwards.

The bot joins as "Whisperr Bot". If the meeting has a lobby, the host needs to admit it, like any other guest.

Check on it

Is the bot in the meeting yet?

Claude reports whether the bot is starting, waiting in the lobby, in the meeting, or finished. If it could not get in, you see that it ended and the reason.

Get a recap afterwards

Read my latest Whisperr conversation and give me the decisions and action items in English.

Claude finds the most recent conversation, reads the transcript with its translations, and writes the recap. Ask for a topic instead of the latest one: "What did the Madrid team say about delivery dates last week?" Transcripts appear in your list a minute or two after the meeting ends. Whisperr saves the transcript by default, so say so if you would rather not keep one.

How the meeting bot behaves

It is a guest, not a hidden recorder. The bot shows up in the participant list as Whisperr Bot. Tell people on the call that you are using a translation and transcription bot, the same courtesy you would extend for any recording.

It needs to be admitted. In a meeting with a lobby or waiting room, the host or a co-host lets it in. Some meetings are set up to refuse automated participants, and if that happens Claude shows the bot as ended with the reason instead of leaving you guessing.

One bot at a time. A subscription runs a single bot. If you ask for a second while one is running, Claude tells you to stop the first. Say "Stop the bot" when the meeting is over, or just let it leave when the meeting ends.

You can stop it any time. Ask Claude to stop it, or remove it from the meeting like any participant.

Keep your key private, and how to disconnect

In Claude Code, the key inside your command works like a password for your Whisperr account's bots and conversations. The command also ends up in your shell history, so do not paste it into chats, screenshots or shared notes. If it leaks, press Regenerate key on the MCP Integration page and the old one stops working at once.

To disconnect Claude Desktop, open MCP Integration in the web app, find Claude under Connected apps, and click Disconnect. Or remove the Whisperr connector in Claude under Customize, then Connectors. To disconnect Claude Code, run the remove command.

Frequently Asked Questions

Do I need a paid Whisperr plan to use this?

Sending a meeting bot needs an active Whisperr subscription. Connecting Claude and reading your saved conversations works on any account, so you can try the connection first. Bots from Claude count toward your subscription and run one at a time.

Which meeting apps work?

Zoom, Microsoft Teams and Google Meet. Paste the meeting link and Claude sends the bot to the right place.

Do I have to pick a source and target language?

No. Pick the two languages used on the call, for example English and Spanish. Whisperr translates both ways by default, so the order does not matter.

Is this different from the Whisperr web app?

It is the same Whisperr, started from a chat. The web app is still the easiest way to follow a call yourself, with captions on your screen. Claude adds the part that is hard to do by hand: sending the bot for you, finding the right conversation later, and turning a long transcript into a recap or a translation in whatever language you need.

Can Claude read my transcripts from earlier recordings?

Yes, as long as they were saved to your Whisperr account. Claude can list and read any saved conversation, from the web app, the iPhone and Android apps, the browser extension or a meeting bot. Bots that Claude sends save their transcript by default.

Who can see my transcripts?

Your saved conversations belong to your Whisperr account, and when you connect Claude it reads them as you, so it can see what you can see and nothing more. Other people cannot see them through your account. One thing to know: what Claude reads becomes part of your conversation with Claude, so Anthropic handles it under the terms of your Claude account.

The live transcript link is different: anyone who has that link can follow the live captions while the meeting runs, so treat it like a meeting link and share it only with the people you want to include. To cut Claude off, disconnect it as described above.

What if the bot cannot get into my meeting?

Ask "Is the bot in the meeting yet?" and Claude shows its status and the reason it ended. The usual causes are a lobby nobody admitted it from, a meeting that blocks automated guests, or an already running bot that needs to be stopped first.

Claude says my account has reached its limit of API keys. What now?

Each connected app uses one key. Open MCP Integration in the web app, disconnect an app you no longer use, and try again.

Try it on your next meeting

The whole flow:

Open the Whisperr web app and go to MCP Integration.
In Claude Desktop, add Whisperr as a custom connector and click Allow. In Claude Code, paste the command from that page and run claude mcp list.
Ask Claude to send a Whisperr bot to your meeting link with the two languages you need.
Admit Whisperr Bot from the lobby and follow along on the live transcript link.
Afterwards, ask Claude for the recap.

Start with the Whisperr web app, and use the same account on iPhone, Android or the browser extension. Everything you record there is waiting for Claude to read.