Circleback

Twelve by Circleback's own support article, against nine in Anthropic's directory snapshot. The three the snapshot omits are SearchActionItems, FindCompanies and ListTags. Circleback's CLI documents the same twelve capabilities command for command, so the vendor list is corroborated twice. Build allowlists from Circleback's article, not from the directory listing.

No. All twelve documented tools read. Every name begins with Search, Read, Get, Find or List, and Circleback's article describes each as finding or retrieving. Circleback's REST API does expose delete for meetings, action items and tags, plus update for meetings — none of those verbs appears among the MCP tools, so the connector reaches a strictly narrower surface than the API key does.

Yes, verbatim and speaker-attributed. GetTranscriptsForMeetings returns full transcripts with speaker labels and timestamps, and SearchTranscripts finds where something was said across the whole archive. Circleback's transcript schema pairs each line with a named speaker. Everyone else in the room consented to Circleback recording, not necessarily to an AI agent replaying what they said.

Exactly one, called user, and it draws no line anywhere. Circleback's RFC 9728 descriptor and its authorization server metadata both advertise scopes_supported as that single value, confirmed live on 2026-08-22. So the consent screen cannot grant meeting titles without also granting verbatim transcripts and connected email. Access narrowing has to happen client-side, by disabling tools.

Yes, if you connected a mailbox to Circleback. SearchEmails queries connected Gmail or Outlook accounts by keyword, sender, recipient or date range. Circleback states it reads email on demand rather than storing copies, so the tool reaches your live mailbox at query time. Disconnecting the account from Settings, Connected accounts is what removes that reach.

It depends which capture mode you use. The Circleback bot joins Zoom, Google Meet, Microsoft Teams and Webex as a visible participant, which is the notice. The desktop and mobile apps record locally with nothing joining the call, and Circleback presents that as the option for when you would prefer the bot not appear. The MCP connector adds no consent check either way.

No. Sharing exists in Circleback, and an automation can share every matching meeting with a whole workspace, but no documented MCP tool triggers one. Automations run on meeting completion, not on tool calls, and none of the twelve tools creates, edits or runs one. The connector reads what automations already produced; it cannot start an outbound path.

The underlying meeting record carries a privateNotes field alongside shared notes, and ReadMeetings is documented as returning detailed meeting information including notes. Circleback does not publish the MCP tool's response schema, so we could not confirm whether private notes cross that boundary. Treat it as unresolved and check one meeting yourself before granting broad access.