Connecting Wave to Other AI Tools
One endpoint puts your Wave meetings inside Claude Code, Cursor, Windsurf, Zed, and any other MCP-compatible tool — with tokens you can revoke whenever you want.
Wave speaks MCP — the Model Context Protocol — so any tool that can connect to a remote MCP server can reach your meetings. Coding agents and editors like Claude Code, Cursor, Windsurf, and Zed all connect to the same endpoint, https://mcp.wave.co, with the same Wave sign-in. It's free on Wave's side.
If you use Claude or ChatGPT, those have their own step-by-step guides.
Add Wave to your client
Run claude mcp add --transport http wave https://mcp.wave.co in your terminal.
Run /mcp inside Claude Code and finish the Wave sign-in in the browser window it opens.
Ask a question — for example, "Summarize every meeting about this repository in the last two weeks."
When your client can't do the browser sign-in
Older clients can't run an OAuth flow. For those, mint a static token and paste it into the client as an Authorization: Bearer wave_mcp_… header.
Open MCP Integration settings. That page isn't linked from the Integrations tab yet, so use the direct link.
Under API Tokens, click Generate Token.
Give it a Token Name that tells you which tool it's for — the field suggests e.g., Claude Desktop.
Copy the token from the Token Created dialog and paste it into your client straight away.
The token is shown exactly once — "Copy this token now. You will not be able to see it again." If you lose it, revoke it and generate a new one. Tokens also stop working one year after they're created, so an integration that quietly goes dark after a long time usually just needs a fresh token.
Manage and revoke access
The same settings page lists every token you've made with its name, its first few characters, when it was created, and when it was last used — a quick way to spot one you no longer recognize.
To cut a tool off, click the trash icon next to its token and confirm Revoke Token. Any application using it loses access immediately. Clients you connected with the browser sign-in are disconnected from the client's own settings.
Manual tokens carry full read and write access. If you want a tool limited to reading, connect it with the browser sign-in instead — Wave issues read and write as separate permissions there.
What a connected tool can do
There are twelve tools, and the split between them matters.
Read (eight tools). Search your sessions by meaning, browse recent sessions with filters for type, date, folder, and tag, list your folders, pull a session's summary and details, retrieve a transcript as plain text, timed segments, or speaker-labeled dialogue, and read a session's action items. Two extras, search and fetch, exist for research-style clients that want citable results.
Write (four tools). Save action items back to a session, create a folder, and add or remove a session from a folder. Nothing else. A connected tool cannot delete a session and cannot edit your recordings or transcripts.
Every call is scoped to the one Wave account that authorized it. Action-item writes replace the whole list for a session, so Wave version-checks them: if you edited the list in the app between the assistant reading it and writing it back, the write is rejected rather than clobbering your edit.
FAQ
Any client that supports remote MCP servers over Streamable HTTP. Wave speaks MCP 2025-11-25 and stays compatible with the 2025-06-18 and 2025-03-26 versions, so older clients keep working.
Check the URL is exactly https://mcp.wave.co with nothing after it, and that the transport is set to Streamable HTTP rather than the local command-line style. Restart the app after adding it.
Ask for a scope in the request itself: "only use sessions in my work folder," or "only search sessions tagged roadmap." Folder names match however you type them; tags have to match exactly, capitalization included. See folders in Wave.
No. MCP access is free on Wave's side. The tool you're connecting may have its own plan requirement.
For the full technical reference — protocol versions, discovery endpoints, and every tool's parameters — see api.wave.co/mcp, or the Wave Agents toolkit for how MCP fits alongside the Developer API and CLI.
Was this article helpful?
Still need help?