Wave API

What is this?

Model Context Protocol is an open standard from Anthropic that lets AI assistants connect to external tools and data sources through a common interface. Wave runs an MCP server at https://mcp.wave.co. Connect your AI client and it gets read-only access to your meeting transcripts, summaries, folders, and semantic search — scoped to the authenticated user.

For building a custom integration from scratch, use the Wave Developer API. For MCP clients (Claude, ChatGPT, editors), this page is the shortest path.

Connect your client

Every client ends up at the same endpoint (https://mcp.wave.co) and the same OAuth login. Pick yours.

Claude

Web, desktop, or mobile

Open Claude →

Open Connectors settings

Settings → Connectors → Add custom connector.

Paste the Wave endpoint

https://mcp.wave.co

Sign in

Claude opens a browser window to app.wave.co. Authorize access. Done — ask Claude something about your meetings.

Claude Code

Anthropic's terminal coding agent

Docs →

Add Wave as a remote MCP server

From a terminal:

claude mcp add --transport http wave https://mcp.wave.co

Authorize

In Claude Code, run /mcp to complete the OAuth flow in your browser.

ChatGPT

OpenAI's connector story is more nuanced than Claude's — there are three paths, depending on your plan and tolerance for beta

OpenAI docs →

Developer Mode (beta, works today)

On Plus / Pro / Team / Enterprise / Edu, enable Developer Mode under Settings → Advanced, then Settings → Connectors → Create, paste https://mcp.wave.co, choose OAuth, sign in. Tools appear via the + button in the composer. This is the closest thing to Claude’s Connectors flow today.

Deep Research connectors (limited)

Deep Research accepts custom MCP servers in Settings → Connectors, but only consumes tools named search and fetch — which Wave doesn’t expose under those exact names. In practice this path doesn’t work for Wave yet.

App Directory (coming)

The zero-setup consumer path is the ChatGPT App Directory. Apps there are installable by any ChatGPT user without Developer Mode. We’re working on submission.

Enterprise / Edu / Team admin publish

Admins can publish Wave as a custom workspace connector via Workspace Settings → Apps → Drafts → Publish. Apps are disabled by default on Enterprise/Edu; an admin must enable connectors first.

Cursor, Windsurf, Zed, and others

Any MCP-compatible client

Client list →

Add a remote MCP server

Follow your client’s MCP setup flow. Wave speaks Streamable HTTP (MCP 2025-11-25) with OAuth 2.0 + PKCE.

Use the endpoint

https://mcp.wave.co

Clients that don’t support OAuth

A handful of older or minimal MCP clients still need a static bearer token. Mint one at app.wave.co/settings/integrations/mcp and attach it as Authorization: Bearer wave_mcp_….

Tools your AI can call

All tools are read-only and scoped to the authenticated user.

search_sessions

Semantic search across every Wave session. Returns relevant snippets.

Inputs: query (string), limit? (default 10, max 50), folder? (id or name)

list_sessions

Recent sessions with metadata. Paginated via cursor.

Inputs: limit?, type?, since?, cursor?, folder?

list_folders

List the folders the user has organized sessions into.

get_session

Title, summary, metadata for a single session.

Inputs: session_id, include_transcript?

get_transcript

Full transcript with speaker attribution.

Inputs: session_id, format? (segments | plain | speaker_labeled)

Example prompts

Meeting prep

"Summarize my last 3 meetings with the Acme team and list any open action items."

Knowledge retrieval

"What did we decide about the API pricing model in last quarter's roadmap review?"

Weekly recap

"Create a summary of all my meetings this week, grouped by project."

Work/personal separation

"Only use sessions in my \"work\" folder. Find discussions about retail media strategy."

Follow-up drafts

"Draft a follow-up email based on my meeting with Sarah yesterday."

Verbatim lookup

"Get the transcript from session sess_01HX... and quote the part where we talked about launch timing."

Protocol details

Endpoint	https://mcp.wave.co
Protocol	Model Context Protocol 2025-11-25 (back-compat to 2025-03-26)
Transport	Streamable HTTP (JSON-RPC)
Auth	OAuth 2.0 + PKCE (preferred), or Bearer token (`wave_mcp_…`)
Discovery	/.well-known/oauth-authorization-server /.well-known/oauth-protected-resource
Data scope	Read-only. Scoped to the authenticated user’s own sessions and folders.

Troubleshooting

Client doesn’t see the Wave integration

Confirm the URL is exactly https://mcp.wave.co (no trailing path). For Claude Desktop, fully quit and reopen the app after adding the connector.

Authentication keeps failing

For OAuth, make sure you complete the login in the browser window your client opens — it needs to post back to the client. For bearer tokens, verify the token prefix is wave_mcp_ and hasn’t been revoked.

No sessions returned

The connector only sees sessions owned by the signed-in user. Check you’re on the same Wave account that holds your recordings. Very new sessions need a few minutes to index.

Search results seem incomplete

Semantic search works best with natural language queries — try rephrasing or adding context. If you use folders to separate work and personal sessions, pass a folder filter.

Wave MCP