MCP App Store
Productivity
Fathom icon

Fathom

by Fathom Video Inc

Overview

Access your meeting summaries, transcripts, and action items so you can ask questions and build deliverables grounded in what was actually said on your calls. No copy-pasting summaries. No context switching. Just better outputs, faster.

Tools

find_person

ChatGPT
Find a person by name across meeting speakers, then return contact info and compact summaries for matched meetings. Searches the speaker index directly. Best used as a preparatory step to identify meetings and context for queries like: "find meetings with Alex", "who is Shreya?", "what does Alice care about?". You may use get_meeting_summary and get_meeting_transcript to lookup additional details for individual meetings. For topic searches like "what did Rich say about the voiceprint script" use search_meetings instead. SCOPE (recorded_by is required — choose based on user intent): - User's own recordings ("What did Alex say in my calls?") → recorded_by = user's email - Accessible / org-wide ("Find meetings with Alex", "prep for my call with Alex") → recorded_by = "anyone" When ambiguous, prefer "anyone" for broader results.

get_identity

ChatGPT
Returns the authenticated user's name and email address. Call this once per session to determine who the authenticated user is. The email is needed only for queries explicitly scoped to the user's own recordings (recorded_by filter), not for every tool call.

get_meeting_summary

ChatGPT
Returns the AI summary of a specific Fathom meeting. Required: recording_id (from list_meetings). When presenting, cite with a working link using the meeting url field.

get_meeting_transcript

ChatGPT
Returns the full transcript of a specific Fathom meeting. Required: recording_id (from list_meetings). Pass url (from list_meetings) to get timestamped deep links in the transcript output. Each speaker segment includes a clickable [MM:SS](url?timestamp=secs) link. Fetch at most 3 transcripts per query — they are large.

get_recording_by_call_id

ChatGPT
Resolve a Fathom call ID to a recording_id plus title, date, and url. Use when the user pastes or types a numeric call ID (e.g. "summarize call 12345"). Pass the returned recording_id to get_meeting_summary, get_meeting_transcript, etc. Returns the same title/date/url shape as list_meetings. For pasted URLs use get_recording_by_url instead. On failure, fall back to using the number directly as a recording_id in get_meeting_summary.

get_recording_by_url

ChatGPT
Resolve a Fathom URL to a recording_id plus title, date, and url. Accepts direct call URLs (/calls/:id) and share links (/share/:token and the /share/h/, /share/i/, /share/p/, /share/u/ variants). Use when the user pastes any Fathom link (e.g. "get the transcript for https://fathom.video/share/123"). Pass the returned recording_id to get_meeting_summary, get_meeting_transcript, etc. Returns the same title/date/url shape as list_meetings. For bare numeric call IDs use get_recording_by_call_id instead.

list_meetings

ChatGPT
List Fathom meetings with filters. Returns recording_id, title, url, recorded_by, calendar_invitees. For team queries call list_teams first. Analytical queries: include_summary:true + include_action_items:true + max_pages:3-5. Does NOT scan meeting content — for finding meetings with a specific person use find_person, for topic searches use search_meetings.

list_teams

ChatGPT
List all Fathom teams the current user belongs to. Returns team names. Use the returned names for the teams filter in list_meetings. Call list_teams first if you need team names — do not guess them.

search_meetings

ChatGPT
Search meeting summaries and titles by topic or keyword. All words in the query must appear somewhere in the meeting text (AND logic). Use this when looking for a specific topic, discussion, idea, or decision — e.g. "voiceprint script", "churn reduction seat contraction", "iOS onboarding". Returns matching meetings with full summary snippets. SCOPE (recorded_by is required — choose based on user intent): - User's own recordings ("search my meetings for churn reduction") → recorded_by = user's email - Accessible / org-wide ("any meeting about iOS onboarding", "search all meetings for X") → recorded_by = "anyone" When ambiguous, prefer "anyone" for broader results. For topic searches that mention a person name AND a topic ("Rich had an idea about X"), use the topic keywords as the query — not the person name.

find_person

Claude

get_identity

Claude

get_meeting_summary

Claude

get_meeting_transcript

Claude

list_meetings

Claude

list_teams

Claude

search_meetings

Claude

App Stats

16

Tools

1

Prompts

Apr 16, 2026

First seen

ChatGPT, Claude

Platforms

Works with

ChatGPT
Claude

Data refreshed daily