Skip to content

Claude App

Bubbles ships a remote MCP server that you add to Claude as a custom connector. Once connected and signed in, Claude can read your teams, bubbles, transcripts, and comments to answer questions like “summarize my standups this week” or “what were the action items from yesterday’s call?” — and it can send the Bubbles notetaker to record a meeting for you.

Before you start

  • The MCP endpoint you’ll add is your Bubbles API origin followed by /mcp:

    https://api-tom.usebubbles.com/mcp
  • Connecting takes no setup: Claude registers itself automatically (dynamic client registration) and completes the OAuth handshake in the background. There is no token to paste, no browser sign-in, and no approval screen. You sign in afterwards, in plain language, inside the chat.

Add Bubbles in claude.ai

  1. In claude.ai, open Settings → Connectors.

  2. Click Add custom connector.

  3. Give it a name (for example, Bubbles) and paste your MCP endpoint URL:

    https://api-tom.usebubbles.com/mcp
  4. Claude connects right away — there is no authorization screen to approve. The connector is now available.

  5. In a chat, open the tools menu and enable Bubbles, then ask Claude to sign you in (see below). Custom connectors are off by default per-conversation.

Sign in inside the chat

A newly added connector is not signed in yet: Claude can see the Bubbles tools, but the ones that read your data return a short “not signed in” message with no data until you sign in. There is no password and no token to copy — signing in happens entirely in the conversation:

  1. Ask Claude to sign you in to Bubbles. Claude asks for your email and Bubbles emails you a sign-in code. (The same step logs in existing users and creates an account for new ones, so you never have to say which you are.)

  2. Read the code back to Claude. That finishes signing you in — on the same connection.

  3. If you’re new, Claude offers to set up a workspace: join one your email domain already uses, or create your own (which may include a free Pro trial).

Once you’re signed in, the read tools return your data and join_meeting works. Claude remembers the connection, so a new conversation is already signed in — you don’t repeat this each time.

What Claude can do once connected

Claude gets six read-only tools plus one write tool (full schemas in the MCP reference):

  • list_bubbles — find your meetings, recordings, and images (filterable by team, type, and date).
  • search_bubbles — search your bubbles by keyword and get the most relevant ones back (matched on title, author name, and the AI-generated meeting notes — so a word discussed in a meeting finds it, even if it isn’t in the title).
  • get_bubble — open one bubble’s details.
  • get_bubble_transcript — read a diarized transcript (chunked for long meetings).
  • get_bubble_comments — read a bubble’s comments.
  • list_teams — list your teams, plans, and channels.
  • join_meeting (write) — send the Bubbles notetaker to join and record a meeting by link.

The six list/get/search tools are read-only — Claude cannot create, edit, or delete anything with them, and it only ever sees bubbles you can read in the product. join_meeting is the only tool that acts: it uses the meetings:join permission your connection carries, and Claude uses it only when you explicitly ask it to record a meeting.

Directory listing status

Troubleshooting

  • “Couldn’t connect” / discovery fails — confirm you pasted your Bubbles MCP endpoint (https://api-tom.usebubbles.com/mcp) exactly, and that it is reachable over the public internet (Claude connects from Anthropic’s cloud, not your device).
  • Tools return “not signed in” — that’s the expected state before you sign in. Ask Claude to sign you in to Bubbles (above), read back the emailed code, and the read tools start returning your data on the same connection.
  • Tools don’t show in a chat — enable the Bubbles connector in the chat’s tools menu; custom connectors are off by default per-conversation.
  • A tool returns nothing after sign-in — you only see bubbles you can read in the product; the same access rules apply to the API and MCP.