How to Connect Wave to Claude
Put your Wave meetings inside Claude — search transcripts, pull summaries, and reference past conversations without leaving the chat.
Connect Wave to Claude and your meetings become part of the conversation. Ask "What did we decide in yesterday's call?" and Claude searches your actual Wave sessions, reads the transcript, and answers from it. Wave is listed in Claude's connector directory as Wave AI Note Taker, so setup is one click and a sign-in — no code.
Before you start
- A Wave account — the same one you record with. Connecting is free on Wave's side.
- A paid Claude plan (Pro, Max, Team, or Enterprise). Connectors aren't available on the free plan.
- On Team and Enterprise workspaces, an owner may need to add the connector at the organization level before you can use it.
Connect Claude to Wave
Works in Claude on the web, desktop, and mobile.
Reading this on your phone? Claude's connector directory can't be opened from a link on iOS or Android, and installing connectors from the phone app is still in beta on Claude's side. The reliable path is to connect once from claude.ai in a browser or in Claude Desktop — the steps below — and Wave appears in the Claude app on your phone the next time you sign in there.
Open the Wave AI Note Taker listing directly, or go to Settings → Connectors, browse the directory, and search for Wave.
Select Connect to Claude.
A browser window opens on Wave. Sign in if you aren't already; there's no extra permission screen to approve. Once you're signed in you're sent straight back to Claude.
In a conversation, switch Wave AI Note Taker on from the + menu, then ask your question.
Claude shows Wave with a Community badge — that's how it labels every third-party connector in the directory. Access stays scoped to the one Wave account you sign in with.
If you'd rather add Wave by hand (or your workspace restricts directory connectors), choose Add custom connector instead, name it Wave, and paste https://mcp.wave.co as the URL — exactly that, with nothing after it. It's the same server either way, so if you already added Wave manually there's no need to switch; just don't keep both, or you'll see two Wave entries.
What Claude can do with your Wave data
Claude gets twelve purpose-built tools and picks the right one for your question. Eight are read-only: search your sessions by meaning, browse recent ones, list your folders, pull a session's summary and details, retrieve a transcript (plain, segmented, or speaker-labeled), and read a session's action items.
Four are focused writes: save action items back to a session, create a folder, and add or remove a session from a folder.
Claude can't delete sessions and can't edit your recordings or transcripts. Writes are limited to action items and folder membership, and everything is scoped to the one Wave account you signed in with.
Ask for what you want
Once it's connected, ask naturally:
- "Prep me for my next call with Acme. Use our last three meetings and surface unresolved decisions."
- "Find the exact part where we discussed launch timing and quote it with the speaker's name."
- "Turn yesterday's product-review decisions into action items and save them to the session."
You can also scope a request so Claude doesn't search everything. Both folders and tags work: "Only use sessions in my work folder" or "Only search sessions tagged roadmap." Tags have to match exactly, including capitalization; folder names don't.
Disconnect or revoke access
Remove the connector in Claude to stop using it. To cut access from Wave's side, open MCP Integration settings — that page isn't linked from the Integrations tab yet, so use the direct link.
FAQ
Custom connectors need a paid Claude plan, and your app may need updating. On Team and Enterprise workspaces the option can also be restricted until an owner adds the connector for the organization.
Check that the URL is exactly https://mcp.wave.co with no extra path. Finish the Wave sign-in in the same browser window Claude opened — a half-finished login in a different browser profile is the usual cause of a loop. Some desktop clients need a full restart after a connector is added.
The connector only sees sessions owned by the Wave account you authorized, so make sure that's the account holding your recordings. A session you just finished may also need a few minutes to process and become searchable.
That's the safety check working. Claude reads your action items with a version number and sends it back with the update. If you edited the same list in Wave in between, the write is rejected instead of overwriting your edit. Ask Claude to re-read the session and try again.
Some tools can't run an OAuth flow. For those, generate a manual wave_mcp_ token and paste it in — see connecting Wave to other AI tools.
Need a hand? Message us in the in-app chat at app.wave.co or email support@wave.co. The always-current technical guide lives at api.wave.co/mcp, and the Wave Agents toolkit covers the API and CLI alongside MCP.
Was this article helpful?
Still need help?