Wave Agents is a set of tools that lets you connect your Wave data to any other application — particularly the AI tools your team is increasingly building and relying on. Everything you record with Wave (transcripts, summaries, action items, audio, speaker-labeled text, semantic search) is accessible from outside the Wave app, so it can flow into whatever workflow you want.

The premise is straightforward: your meetings are the richest source of context about your work, and that context is most useful when the tools you already use can reach it. An AI assistant that can quote your actual conversations is meaningfully more useful than one that can't. A CRM that updates itself from a recording you just finished is meaningfully better than one you have to update by hand. Wave Agents exists to make those connections trivial to set up.

It's organized as three surfaces — three different shapes of the same underlying access. Pick whichever fits the tool you're connecting.

The Model Context Protocol is the emerging standard for letting AI assistants talk directly to outside data sources. With Wave's MCP server, assistants like Claude, ChatGPT, Cursor, Claude Code, Windsurf, and Zed can search your meetings, pull summaries, and reference past conversations on demand. Setup is a single URL — no code required.

Setup guide: api.wave.co/mcp

A standard REST API for programmatic access to your sessions, transcripts, summaries, and search. Use it to build custom agents, sync sessions into a CRM, generate analytics, or power any workflow that benefits from meeting data.

The API also includes webhooks — a way for Wave to tell your system the moment something new happens, instead of your system having to keep checking. The second a recording finishes processing, Wave pings whatever URL you give it, so a Slack post can fire, a CRM can update itself, or your custom agent can get to work — all without anyone clicking anything.

API reference: api.wave.co/reference

A command-line tool (@waveai/cli) that makes Wave data available in any shell-driven workflow — scripts, cron jobs, pipelines, or ad-hoc one-liners. Installs via npm and authenticates with a browser-based OAuth flow.

CLI docs: api.wave.co/cli

All three share the same account and the same permissions model. The full overview lives at wave.co/agents, and the developer hub — with documentation for every endpoint and command — is api.wave.co.

Nothing is connected until you connect it. All three surfaces use OAuth or scoped tokens, are read-only by default, and can be revoked at any time from Settings → Integrations.

For setup help, contact us via the in-app chat in app.wave.co or email [email protected]. For technical questions about building on the API, CLI, or MCP, the documentation at api.wave.co is the most complete reference.