otheroauth2

Otter.ai MCP

Otter.ai MCP lets agents retrieve the authenticated user's profile, search authorized meetings and conversations, and fetch complete transcripts for analysis and summarization.

Verdict

The Otter.ai MCP connects your team's meeting transcripts and conversation intelligence to Switchy. @mention it to search past meetings, pull speaker insights, extract action items, or summarize what was discussed in a specific call. Most valuable for teams who record standups, client calls, or design reviews and need to reference decisions without re-watching video. Requires OAuth with read access to your Otter workspace; if your org restricts API access or uses Otter's free tier, some features may be limited.

Common use cases

  • Surface action items from last week's standups
  • Find who mentioned a feature in client calls
  • Summarize a design review without rewatching
  • Pull verbatim quotes from a sales demo
  • Track recurring themes across sprint retros

Integration

Vendor
Otter.ai MCP
Category
other
Auth
OAUTH2
Composio slug
otter_ai_mcp

Tools

Per-tool listings haven't synced yet for Otter.ai MCP. The connection itself works - your Project can already @-mention it. Tool descriptions will fill in on the next Composio ingest.

Setup

Setup guide

  1. 11. Inside any Switchy Project, click the '+' icon in the chat input and select 'Connect MCP'. 2. Search for 'Otter.ai' and click 'Connect'. 3. You'll be redirected to Otter's OAuth consent screen—log in with the account that has access to the meetings you want to query. 4. Grant read permissions for transcripts and conversations (Otter will list the exact scopes). 5. After authorizing, you'll return to Switchy and see 'Otter.ai MCP connected' in your Project settings. 6. Test the connection by typing '@Otter.ai list my recent meetings' in the chat—if it returns a list of transcripts, you're ready. 7. From now on, @mention Otter.ai in any message to search transcripts, pull quotes, or summarize discussions from recorded calls.

What teammates see: by default, memories from Otter.ai MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

List Recent Meetings

@Otter.ai show me the ten most recent meeting transcripts in my workspace

Extract Action Items

@Otter.ai pull all action items from the meeting titled 'Sprint Planning - Jan 15'

Find Speaker Mentions

@Otter.ai find every mention of 'pricing model' in meetings from the last two weeks

Summarize a Call

@Otter.ai summarize the 'Client Kickoff - Acme Corp' meeting and list any unresolved questions

Compare Retro Themes

@Otter.ai compare the last three sprint retros and tell me which issues came up more than once

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@otter.ai pull the transcript from yesterday's standup meeting and highlight any action items mentioned

Output

Retrieved transcript from 'Daily Standup - Jan 15' (14:32 duration). The meeting included 4 participants. Action items identified: Sarah committed to finishing the API documentation by Friday; Mike will review the staging deployment today; Team agreed to schedule a retro for next Tuesday. Full transcript shows discussion of sprint progress, a blocker with the payment gateway, and clarification on the new feature spec.

Notes

This example shows transcript retrieval and AI-assisted parsing. Otter.ai requires OAuth consent with read access to your meeting recordings. The quality of action-item extraction depends on how clearly commitments were stated during the meeting — vague discussions may not surface as discrete tasks.

Prompt

@otter.ai search all my transcripts from the last two weeks for mentions of 'budget approval' and summarize what was decided

Output

Found 3 meetings mentioning 'budget approval': (1) Jan 8 Leadership Sync — CFO approved Q1 marketing spend up to $45K, pending final deck review. (2) Jan 10 Product Planning — Budget for contractor hours deferred until Feb board meeting. (3) Jan 14 All-Hands — No new budget discussion, brief mention in Q&A about hiring freeze. Consensus: marketing approved, contractor budget still pending.

Notes

Demonstrates cross-meeting search and synthesis. This requires OAuth access to your full Otter.ai library. Search accuracy depends on transcription quality — accents, background noise, or jargon may reduce match precision. Results reflect meetings you have access to, not org-wide recordings unless shared.

Prompt

@otter.ai create a summary of today's client call and share it with the #sales channel format

Output

Generated summary for 'Acme Corp Discovery Call - Jan 16' (42 min). Key points: Client needs integration with Salesforce and Slack by March; current pain point is manual data entry across 3 tools; budget range $20-30K annually; decision-maker is VP Ops, final approval requires CFO sign-off. Next step: send proposal by Jan 23. Summary formatted for Slack sharing with participant names and timestamps for key quotes.

Notes

Shows post-meeting summarization and formatting. This example assumes the MCP can generate summaries from recent transcripts — actual implementation may require you to specify the meeting by ID or timestamp. Sharing functionality depends on whether the MCP supports direct posting or just returns formatted text for manual distribution.

Use-case deep-dives

Post-meeting action item extraction

When Otter.ai MCP works for async meeting follow-up

A 6-person remote team runs three Zoom calls a week and needs action items surfaced without manual note-taking. The Otter.ai MCP connects via OAuth2, so any team member can query transcripts directly in Switchy without leaving the workspace. The win is speed: instead of scrolling through Otter's web UI or asking "who said what about the API deadline," you ask Switchy and get timestamped excerpts in seconds. The trade-off is scope—if your team records calls outside Otter (Slack huddles, in-person whiteboard sessions), this MCP won't see them. It's the right call when Otter is already your single source of truth for meeting audio and you want that context available in every AI conversation your team has.

Customer interview synthesis for product teams

Using Otter transcripts to build feature briefs

A 4-person product team conducts 8-10 customer interviews per sprint and needs to turn raw transcripts into feature briefs without re-listening to hours of audio. The Otter.ai MCP lets Switchy pull transcript data directly, so you can ask "summarize pain points from last week's interviews" and get a synthesized view across multiple calls. The advantage is consolidation—no copy-pasting from Otter into Notion or Google Docs. The limitation is that the MCP doesn't yet expose speaker labels or sentiment tagging (as of this input snapshot), so nuanced analysis still requires manual review. This setup wins when your interview volume is high enough that manual synthesis is a bottleneck but low enough that you're not building a dedicated research ops pipeline.

Sales call coaching and onboarding

When Otter MCP helps new reps learn from recorded calls

A 3-person sales team onboards a new rep and wants them to learn objection-handling patterns from the last 20 discovery calls without sitting through full recordings. The Otter.ai MCP gives Switchy access to those transcripts, so the new rep can ask "show me how we handled pricing objections in Q1" and get relevant excerpts with context. The benefit is searchability at scale—Otter's native search is good, but querying across calls in natural language inside Switchy is faster for pattern-spotting. The boundary is coaching depth: if you need call scoring, talk-time ratios, or CRM integration, you're better off with a dedicated sales intelligence tool. Use this MCP when your coaching workflow is transcript-first and your team already lives in Otter for call recording.

Frequently asked

What does the Otter.ai MCP do in Switchy?

It connects your Otter.ai account so AI assistants in Switchy can access your meeting transcripts, summaries, and speaker notes. Your team can ask questions about past meetings, pull action items, or reference specific conversations without leaving the workspace. The MCP handles OAuth authentication so you don't manage API keys manually.

Do I need admin access to my Otter.ai account to connect it?

No, any Otter.ai user with a valid account can connect through OAuth. You'll authorize Switchy to read your transcripts and meeting data during the OAuth flow. If your organization uses Otter.ai Business, check with your admin about any SSO or access policies that might affect third-party integrations.

Can the MCP create or edit transcripts in Otter.ai?

No, this integration is read-only. AI assistants can retrieve and analyze existing transcripts but can't start recordings, edit speaker labels, or modify summaries. If you need to change something, do it directly in Otter.ai — those updates will appear in Switchy once synced.

Why use this instead of just searching Otter.ai myself?

The MCP lets AI assistants cross-reference meeting transcripts with other data sources you've connected in Switchy — like Slack threads, GitHub issues, or Google Docs. Instead of manually copying context between tools, you ask one question and get answers that span multiple systems. It's faster for teams working across fragmented information.

Who on my team should connect the Otter.ai account?

Connect the account that owns the meeting transcripts your team needs to reference. If you record meetings under a shared account, connect that one. If everyone records individually, each person can connect their own Otter.ai account to Switchy. The MCP only accesses transcripts the connected user can already see.

More other MCPs

See all other MCPs →

Data last verified 61 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.