MCP Server

Your meetings, inside your AI tools.

Reverbic speaks the Model Context Protocol. Point Claude, Cursor, or any MCP-compatible client at https://reverbic.ai/api/mcp and it can read your meetings, transcripts, action items, and decisions — with your permission, scoped by key.

1. Get a key

In the web app, open Settings → MCP and generate a key. Keys start with rvb_, are shown once, and can be revoked at any time. Requires an org admin on the Team plan or above.

Every request authenticates with Authorization: Bearer rvb_… — the transport is streamable HTTP (JSON-RPC 2.0 over POST).

2. Connect your tool

Claude Code — one command:

claude mcp add --transport http reverbic \
  https://reverbic.ai/api/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Claude Desktop — only speaks stdio, so route through the official mcp-remote proxy in claude_desktop_config.json, then restart:

{
  "mcpServers": {
    "reverbic": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://reverbic.ai/api/mcp",
        "--header",
        "Authorization:Bearer YOUR_KEY"
      ]
    }
  }
}

Cursor / native HTTP clients — connect directly:

{
  "mcpServers": {
    "reverbic": {
      "url": "https://reverbic.ai/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

3. Available tools

All tools are read-only. Each requires its scope on the key — keys carry every scope by default; mint narrower ones via the API if you want tighter access.