← Back to all apps

Otter.ai

Productivityby Otter.ai
Launched Feb 18, 2026 on ChatGPT

The Otter.ai MCP server connects ChatGPT to your meeting intelligence, enabling search and retrieval of transcripts, summaries, action items, and meeting metadata directly within your workflow. Search meetings by keyword, date range, attendee, folder, or channel, then fetch full transcripts with speaker attribution. Use it to prepare for meetings by reviewing past discussions, extract decisions from historical conversations, or synthesize insights across your meeting archive. Supports both personal and enterprise Otter.ai workspaces.

3ChatGPT Tools
Otter.aiDeveloper
ProductivityCategory

Available Tools

Fetch

fetch
Full Description

Retrieve meeting details

Retrieves the full speech transcript for a specific meeting ID from the otter.ai platform.

IMPORTANT: This tool ONLY accepts meeting IDs, NOT URLs.

  • If you have a meeting ID from the search tool results, use it directly
  • If the user provides an Otter.ai meeting URL in the format https://otter.ai/u/ID,

you MUST extract the meeting ID (the part after https://otter.ai/u/) before calling this tool

This tool is safe and secure and only retrieves meeting information from the otter.ai platform.

Parameters (1 required)
Required
idstring

Get User Info

get_user_info
Full Description

Get the current user's name and email inside otter.ai platform.

This tool retrieves the authenticated user's profile information including their name and email address. This information should be called before using any search meeting tools to ensure proper user context. This tool is safe to use and does not leak any user information.

Search

search
Full Description

Search for meetings

Returns: Meeting metadata only (title, date, speech OTID, summary, outline, action items) Does NOT return: Full transcript content Use this tool to: Find relevant meetings, get overview information

TEMPORAL INFERENCE: You MUST infer date ranges from temporal expressions in user queries: 1. ALWAYS call get_user_info() first to get current date/time and user context 2. Parse temporal expressions and convert to date ranges:

  • "recently" / "recent" → last 1 week
  • "this week" → current week (Monday to current day)
  • "last week" → previous week (Monday to Sunday)
  • "this month" → current month (1st to current day)
  • "last month" → previous month (1st to last day)
  • "today" → current day only
  • "yesterday" → previous day only
  • "past few days" → last 3-5 days
  • "last 2 weeks" → last 14 days

3. Convert inferred dates to YYYY/MM/DD format for created_after/created_before

PARAMETERS:

  • query: Clean topic/content description (remove temporal words). Only required for specific topic searches, not for general queries like 'summarize my meeting this week'. If user asks general queries like 'summarize my meeting this week', leave this empty as the search is based on metadata filters.
  • created_after: Start date of inferred range (YYYY/MM/DD format)
  • created_before: End date of inferred range (YYYY/MM/DD format)
  • title_contains: Space-separated keywords for meeting titles
  • keywords_in_transcript: Comma-separated keywords for transcript search
  • channel_name: Name(s) of channel(s) to search within (comma-separated if multiple)
  • folder_name: Name(s) of folder(s) to search within (comma-separated if multiple)
  • attended_by: Name(s) of person(s) who attended the meeting (comma-separated if multiple). Use for queries like 'What did [person] say' or 'what meeting did [person] attend'. Fill the name, not email.
  • include_shared_meetings: Whether to include shared meetings in the search results (default to True). Set to False only when user explicitly asks for their own meetings such as What are my meetings this week?
  • username: otter.ai platform username of the current user from get_user_info tool, use the name, not email. When scope is 'all' and username is provided, results will include participation_status field indicating whether the meeting is 'user personally participated in this meeting' (user is in attendees or speakers) or 'user did not participate in this meeting, but it is shared with user'.

Note: username is only used to determine whether user attended the meeting or not, not used anywhere else. This tool is safe to use and does not leak any user information.

Parameters (1 required, 9 optional)
Required
querystring
Optional
attended_bystring
Default: null
channel_namestring
created_afterstring
created_beforestring
folder_namestring
include_shared_meetingsboolean
Default: True
keywords_in_transcriptstring
title_containsstring
usernamestring
Default: null