The Wave Agents Toolkit: Connect Your Data to Any Other Tool

Everything Wave AI captures (transcripts, summaries, action items, speaker labels, audio and video files) can be read from outside the Wave app. Wave Agents is the name for the three ways to do that: MCP for AI assistants, a REST API for code you write, and a command-line tool for scripts. All three run against your own account, use access you grant and can revoke, and are free on every Wave plan.

Pick the one that matches the tool you're connecting.

MCP — for AI assistants

The Model Context Protocol lets an AI assistant query your Wave library during a conversation. Claude, ChatGPT, Claude Code, Codex, Cursor, Grok, Muse, Perplexity, and most coding editors all speak it. Setup is a single URL — https://mcp.wave.co — and a browser sign-in. No code, no config files.

Once connected, the assistant can search your meetings by meaning, list recent sessions, open a summary, pull a speaker-labeled transcript, read action items, and find the sessions a person was in. It can also:

• write action items back to a session
• edit a session's title, notes, summary, and tags, and mark it as a favorite
• create, rename, and delete folders and file sessions into them
• share a session when you ask
• import a recording into Wave, if you give it that separate permission (see below)

It cannot delete a session or change a transcript or audio, and deleting a folder never deletes the sessions in it. Wave's MCP server has 23 tools in all; the full list is at api.wave.co/mcp.

You can keep an assistant out of your personal recordings by scoping requests to a folder or a tag. "Only use sessions in my Work folder" works, because the underlying tools accept folder and tag filters. See all about folders in Wave.

Setup guides: Claude, Claude Code, ChatGPT, Codex, Cursor, Grok, Muse, and other AI tools, including Gemini CLI.

Ready-made prompts

Wave comes with six prompts you can start from instead of typing a request. They show up in tools that support MCP prompts: in Claude, open the + menu in a chat; in Claude Code, type / and look for the Wave entries.

The Wave plugin for Claude Code and the Wave extension for Gemini CLI add the same six as skills.

Editing sessions

Ask the assistant to rename a session, tidy its notes, rewrite its summary, change its tags, or mark it as a favorite. Only what you ask for changes. A new title or summary can't be saved while Wave is still processing the recording, because processing would overwrite it; the assistant will say so, and you can try again a few minutes later. Notes, tags, and favorite can be changed at any time.

Importing recordings

An assistant can add a recording to Wave for you: from a link to an audio or video file (for example a podcast episode or a direct download link), or, in tools that can upload a local file such as Claude Code and Codex, from a file on your computer. Wave then transcribes and summarizes it like any other import.

Importing needs its own permission, separate from reading and writing. Wave asks for it on a consent screen that lists Import recordings into Wave (uses your import allowance). The tool can't import anything until you tick I started this connection from [tool] myself and select Allow [tool]. Imports count against the same import allowance as importing in the Wave apps. If your tool never asks for this permission, you can use a personal access token with Allow importing recordings ticked instead (see other AI tools). ChatGPT doesn't import recordings.

Developer API — for code you write

A REST API at https://api.wave.co/v1, authenticated with a scoped token you create in Wave settings. Use it to sync sessions into a CRM, back up transcripts, build a dashboard, or feed a custom agent.

It covers listing and filtering sessions, summaries, transcripts, action items, semantic search, folders, sharing, stats, bulk export of up to 50 sessions in one request, signed download URLs for audio and video, and importing recordings. It also pushes webhooks to your server the moment a recording finishes processing, optionally with the transcript and action items included, so nothing has to poll.

Start here: Wave Developer API.

CLI — for the terminal

@waveai/cli installs with npm and gives you a wave command for scripts, cron jobs, and one-off exports. Every command that returns data has a --json flag, so it composes with the rest of your shell.

Start here: Wave CLI.

Slack — for asking where your team already talks

In Slack, ask Wave about your meetings in a DM, with @Wave in a thread, or with /wave. Answers come only from your own recordings and stay private until you share them, and Wave can post a recap after each recording.

Start here: Use Wave in Slack.

Zapier — for automations without code

Zapier fires a New Session Ready trigger each time a session finishes processing, with the title, summary, speaker-labelled transcript, notes and a link. Use it to post summaries to a channel, add rows to a sheet, or log a note in your CRM, without writing code. Zapier signs in with your Wave account, so there is no token to manage.

Start here: Automate Wave with Zapier.

Sharing

All three also work with sharing. They can read sessions other Wave users shared with you, read-only, and share your own sessions: create an invite link, email invites, see who has access, and remove people. An AI assistant confirms before it shares anything. See Sharing Sessions from Claude, ChatGPT, the API and the CLI.

What these tools can and can't do

Nothing is connected until you connect it, and every connection is scoped to your own account. The only other people's recordings it can reach are sessions they chose to share with you.

Permissions are not read-only by default. When you create an API token you tick exactly the permissions you want, and the list includes Write sessions and action items, Delete sessions, Manage folders, and Share sessions and manage access. Importing recordings is a separate permission that's never included unless you choose it. Signing the CLI in through your browser grants every permission, including deleting sessions. MCP is the narrow one: it can write action items, edit sessions, organize folders, and share sessions, but it can't delete a session, and it can import only if you allowed that.

Revoke anything at any time on the web. AI apps you signed in to are listed under Settings → Integrations → Connected AI apps, each with its access, when you connected it, and when it was last used; select Disconnect and it loses access right away. Personal access tokens for AI tools are on the same page under Advanced: personal access tokens. API and CLI tokens are under Settings → Developers → API tokens and webhooks.

Hand the docs to your AI assistant

Every page on api.wave.co has a copy button in the header — Copy integration docs, or Copy MCP docs on the MCP page. It copies a plain-text description of the whole platform — endpoints, scopes, payload shapes, examples — that you can paste into Claude or ChatGPT and say "write me the integration." The same text lives at api.wave.co/llms.txt, and the full interactive reference is at api.wave.co/reference.

Support

For setup help, use the in-app chat at app.wave.co or email support@wave.co. For questions about building on the API, MCP, or CLI, api.wave.co is the most complete and most current reference.