Fathom
Search Fathom call recordings, AI summaries, and action items across your meetings. Sign in with Fathom to connect.
What Fathom exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the fathom__ namespace. Your agent never loads them all — it searches, and gets the few that match.
fathom__find_person3 arguments · 2 required
Find Person
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.
Required
namerecorded_byfathom__get_identityno arguments
Get Current User Identity
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.
fathom__get_meeting_summary1 argument · 1 required
Get Meeting Summary
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.
Required
recording_idfathom__get_meeting_transcript2 arguments · 1 required
Get Meeting Transcript
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.
Required
recording_idfathom__get_recording_by_call_id1 argument · 1 required
Get Recording by Call ID
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.
Required
call_idfathom__get_recording_by_url1 argument · 1 required
Get Recording by URL
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.
Required
urlfathom__list_meetings8 arguments
List Meetings
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.
fathom__list_teamsno arguments
List Teams
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.
fathom__search_meetings4 arguments · 2 required
Search Meetings
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.
Required
queryrecorded_by
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Switch Fathom on
Authorize it from your library; the grant is yours and stays yours.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.devOthers in the same category.
They share the endpoint, so having more than one on costs you nothing in context — the search decides which is relevant.
