Wave for Agents · MCP

The Wave MCP server

Plug Wave directly into Claude, ChatGPT, Cursor, and any other client that speaks the Model Context Protocol. Your AI assistant can list your recordings, fetch transcripts, and search across them — under your account, with your permissions, and with no integration code on your side.

Drop-in for MCP clientsPoint your Claude, ChatGPT, or Cursor MCP config at mcp.wave.co. Authorize once via OAuth, and Wave's tools become available to your agent.
Sessions, transcripts, searchThe MCP server exposes the same operations as the API: list and fetch sessions, retrieve transcripts, and run semantic search across the user's recordings.
OAuth-scoped, revocableAccess is per-user via OAuth 2.0 with PKCE. Tokens prefixed wave_mcp_ can be revoked from your Wave account at any time.

What your agent can do

Connect from Claude

{
  "mcpServers": {
    "wave": {
      "url": "https://mcp.wave.co"
    }
  }
}

Drop this into your Claude desktop config (or the equivalent for your MCP client), restart, and authorize Wave in the OAuth flow that opens. Your assistant now has access to your Wave content.

How it’s secured

OAuth 2.0 with PKCE. Tokens are hashed server-side; only the holder of the access token can use it. OAuth discovery endpoints are published at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource so MCP clients can configure themselves automatically.

Other developer surfaces

Same account, three ways in: REST API for code, CLI for shell, and this MCP server for agents.

Wave app screenshot showing meeting transcription
Wave AI note taker background pattern
Start today

Wave. Catch every word