Otter.ai
by Otter.ai
Search your Otter meeting transcripts and open full speech transcripts in your AI assistant. Three tools, and for once the directory count is exactly right. Otter is the only meeting connector in this catalogue whose OAuth scopes name the data and say read — but its privacy policy also describes training on de-identified recordings.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Otter.ai via MCP
https://mcp.otter.ai/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Otter.ai Tools & Capabilities (3)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Reach is wider than "meetings you attended". Otter states MCP reaches everything you captured plus everything shared with you by other workspace users. Auto-share and channel membership can put colleagues' recordings in that set without a per-meeting decision by either party.
- Auto-sharing to channels cannot be turned off workspace-wide. Otter documents admins as able to stop automatic sharing to calendar guests, while members can still auto-share conversations to channels from the individual calendar event.
search's field-level scope is undocumented. Otter does not publish whether it matches titles, transcript text or both. Its own capability list and examples point at full text, but we could not confirm it and do not assert it.- No result cap, rate limit or pagination is documented. An agent builder cannot size a bulk sweep from Otter's documentation the way Fireflies' 50-result ceiling or Granola's stated request rate allow.
- Direct microphone recording produces no participant signal. Otter documents recording from a browser or phone mic with no bot, no attendee-list entry and no in-meeting chat message. The MCP server does not distinguish those conversations from bot-recorded ones.
- Auto-join can add the bot without a per-meeting decision. One documented default joins every calendar event carrying a Zoom, Meet or Teams link; enabling it once on a recurring event applies to the series.
- Pre-meeting notification is optional, and the strongest form is licence-gated. Pre-recording emails are a setting rather than a default; the Teams permissions page requiring active agreement needs the Otter for Outlook extension and a Microsoft Enterprise licence.
- There is no default retention window. Otter documents custom policies only, set through an account manager with a 24-hour minimum. Absent one, conversations persist.
- Deleting the recording does not delete the notes. Otter's own example states that after audio and video expire, the transcript, summary and action items remain accessible.
- Otter's privacy policy describes training on de-identified recordings and transcriptions, and notes those transcriptions may contain personal information. Read the primary document if this axis matters to your choice.
- No API key exists. Otter states there is no public API key, so clients that cannot do browser OAuth cannot connect at all.
- ChatGPT desktop cannot make the connection. Otter documents the connection as needing to be made in the ChatGPT web version first.
- We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas and no safety annotations were readable to us. Every read-only claim here is Otter's documentation plus the advertised scopes.
- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, but the gated endpoint blocked our own
prompts/list, so we cannot say whether the server serves any. - The connector adds no consent check. Notetaker's visible presence is the notice mechanism on calendar meetings, but nothing in the MCP layer verifies that participants understood a transcript would be made or read by an agent.
Frequently asked questions
Whose meetings can the Otter MCP connector read?
Everything you captured in Otter, plus every conversation another workspace member shared with you. Otter states both halves plainly in its MCP article. The second half is the one that surprises people: auto-share can push a recording to calendar guests or a channel without either side deciding per meeting, so your reachable corpus can include conversations you never attended.
Does Otter MCP search the full transcript text or only meeting titles?
Otter does not publish the field-level scope of search, so we cannot state it. Otter describes the tool as searching for meetings and returning an overview, and its own MCP article advertises searching transcripts across all time periods. Its Enterprise guidance adds that search results are limited to content the user has permission to see. No result cap is documented.
Is the Otter MCP server really read only?
Yes, on everything we could check. All three documented tools read, both advertised OAuth scopes end in read, and no write tool appears in Otter's documentation despite the product being able to share conversations and generate summaries. Otter also states it has no public API key, so the only credential is a browser OAuth session you can revoke.
Does Otter train its AI models on my meeting recordings?
Otter's privacy policy describes training its proprietary AI technology on de-identified audio recordings and on transcriptions, and notes those transcriptions may contain personal information. It lists data labeling providers who use shared data to build training and evaluation sets. That is a materially different posture from meeting connectors whose vendors state no training by default.
Do meeting participants know Otter is recording them?
For calendar meetings, usually yes. Otter documents Notetaker joining as a named participant and posting a chat message linking the live transcript, plus optional pre-recording emails to every invitee. Recording straight from a laptop or phone microphone produces none of those signals. Otter recommends notifying participants and points at jurisdictions requiring all-party permission.
How long does Otter keep meeting recordings and transcripts?
Indefinitely unless a workspace admin sets a retention policy through an Otter account manager, with a minimum of 24 hours. Admins can expire audio and video on one clock and transcripts on another. Otter's own example notes that after the audio expires the summary and action items remain accessible, so derived notes outlive the recording.
What OAuth scopes does the Otter MCP server request?
Two, and both name data and say read: profile:read and conversations:read. We read them live from the protected-resource descriptor and the authorization-server metadata at otter.ai on 2026-08-19. That makes Otter the only meeting connector in this catalogue whose authorization screen can express what an agent reaches and that it only reads.
Can I use an API key instead of OAuth for Otter MCP?
No. Otter states it currently has no public API key and directs anyone needing one to its support team. Every documented setup path, for Claude, ChatGPT, Cursor and Perplexity alike, ends with signing in to Otter and authorizing access. That removes the durable pasted-credential problem that API-key meeting connectors carry.
Sources
- Otter MCP Server — https://help.otter.ai/hc/en-us/articles/35287607569687-Otter-MCP-Server (fetched 2026-08-19 via the Zendesk Help Center article JSON API; three tools, corpus statement, no public API key) · retrieved 2026-08-19
- Automatically add Otter Notetaker to your meetings — https://help.otter.ai/hc/en-us/articles/13674910923671-Automatically-add-Otter-Notetaker-to-your-meetings (fetched 2026-08-19; five auto-join default settings) · retrieved 2026-08-19
- Choose which meetings Otter Notetaker records — https://help.otter.ai/hc/en-us/articles/26010355877911-Choose-which-meetings-Otter-Notetaker-records (fetched 2026-08-19; recurring-series behaviour, 30-minute lead time) · retrieved 2026-08-19
- Recording Permissions with Otter — https://help.otter.ai/hc/en-us/articles/39339238308503-Recording-Permissions-with-Otter (fetched 2026-08-19; named participant, in-meeting chat announcement, Teams permissions page, host removal) · retrieved 2026-08-19
- Enforce pre-meeting recording notifications — https://help.otter.ai/hc/en-us/articles/13353091821591-Enforce-pre-meeting-recording-notifications (fetched 2026-08-19; Enterprise-only, overrides individual settings, 5-10 minutes before start) · retrieved 2026-08-19
- Record a conversation — https://help.otter.ai/hc/en-us/articles/360048269733-Record-a-conversation (fetched 2026-08-19; direct microphone capture in browser and mobile app) · retrieved 2026-08-19
- Turn off auto-share for conversations & meetings — https://help.otter.ai/hc/en-us/articles/14952683922711-Turn-off-auto-share-for-conversations-meetings (fetched 2026-08-19) · retrieved 2026-08-19
- Manage Workspace auto-share settings — https://help.otter.ai/hc/en-us/articles/32589333117591-Manage-Workspace-auto-share-settings (fetched 2026-08-19; channel auto-sharing cannot be disabled workspace-wide) · retrieved 2026-08-19
- Channels Overview — https://help.otter.ai/hc/en-us/articles/360049379794-Channels-Overview (fetched 2026-08-19; channel members inherit access to all conversations in the channel) · retrieved 2026-08-19
- How Privacy and Data Control Work in Otter Enterprise Trials — https://help.otter.ai/hc/en-us/articles/39341194005271-How-Privacy-and-Data-Control-Work-in-Otter-Enterprise-Trials (fetched 2026-08-19; permission-based search, no organisation-wide search) · retrieved 2026-08-19
- Set a custom Data Retention policy — https://help.otter.ai/hc/en-us/articles/19500988656279-Set-a-custom-Data-Retention-policy (fetched 2026-08-19; 24-hour minimum, separate audio and transcript clocks, summaries survive) · retrieved 2026-08-19
- Data security and privacy policies — https://help.otter.ai/hc/en-us/articles/360048258953-Data-security-and-privacy-policies (fetched 2026-08-19; AWS US region, AES-256 at rest) · retrieved 2026-08-19
- Otter privacy policy — https://otter.ai/privacy-policy (fetched 2026-08-19; training on de-identified audio recordings and on transcriptions, data labeling providers) · retrieved 2026-08-19
- Live RFC 9728 protected-resource descriptor — https://mcp.otter.ai/.well-known/oauth-protected-resource (fetched 2026-08-19; the path-append and path-insert forms both return 404) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://otter.ai/.well-known/oauth-authorization-server (fetched 2026-08-19; the MCP host serves no RFC 8414 document at any of the three forms) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19: a POST to the endpoint returns HTTP 401 with
www-authenticatenamingresource_metadataat the root well-known URL and no scope parameter · retrieved 2026-08-19 otter.ai/robots.txtallows all agents with a short disallow list covering share and note paths, and names a sitemap; it carries noContent-Signalaxes.otter.ai/llms.txtreturns 200 but serves the marketing single-page-app shell rather than a machine index, and the.mdsuffix on a help-centre article returns 403 (fetched 2026-08-19) · retrieved 2026-08-19- Anthropic connector directory — https://claude.ai/directory/bb74915f-d284-4590-a208-ae06447b37af (snapshot 2026-08-16; three tools, no prompt names,
permissionslabel "Read only") · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Otter.ai
- Tools
- 3
- Domain
- mcp.otter.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.