fathom-mcp-adapter
Provides tools to interact with Fathom meetings and transcripts, allowing listing recent meetings, retrieving the latest meeting, and fetching raw transcripts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fathom-mcp-adapter list my recent meetings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
fathom-mcp-adapter
Read-only MCP server that exposes Fathom meetings + transcripts as tools, for use
by /updateP1 (and other skills) in the TICKETS workspace.
This is a private, standalone adapter: its own git repo, its own .env. It is
not part of ia-tooling and does not depend on its stack — it only makes HTTPS
calls out to the Fathom REST API (https://api.fathom.ai/external/v1). It was scaffolded by
cloning the structure of ia-tooling/services/zendesk-mcp-adapter.
Architecture
The adapter is the MCP server. Internally it calls the Fathom REST API directly (just as the Zendesk adapter calls Zendesk's REST API). MCP servers are not chained to one another.
Auth: per-user API key sent as the
X-Api-Keyheader. The key is scoped to one user (their own meetings + meetings shared to their Team), which provides data isolation between teammates. Rate limit: 60 req/min.The adapter returns the raw transcript. The who/what/when summary is produced by the
/updateP1skill, never by a tool here.There is no title/keyword search in the Fathom API. To find a specific meeting, list recent meetings (optionally narrowing by
created_after/recorded_by) and let the skill filter by title/date/invitee.
Related MCP server: Fathom AI MCP
Tools
Tool | Purpose |
| Config/connectivity check (makes one authenticated call). |
| List recent meetings, newest first. Filters: |
| The single most recent meeting (the 90% case for |
| Raw transcript for a |
Each meeting record includes title, recording_id, created_at, url (private,
login-gated) and share_url (team-shareable). For the internal timeline reference
use share_url, never url.
Setup
npm install
cp .env.example .env # then fill in FATHOM_API_KEY
npm test
npm start # speaks MCP over stdioFATHOM_API_KEY must come from .env (which is git-ignored) — never hardcode it.
Wiring into the TICKETS MCP session
Build the image and add a fathom entry to the TICKETS .mcp.json, alongside
zendesk / vectordb / github. It does not need the ia-tooling_default
network (HTTPS egress only).
docker build -t fathom-mcp-adapter .// .mcp.json (TICKETS)
{
"mcpServers": {
"fathom": {
"command": "docker",
"args": ["run", "--rm", "-i", "--env-file", "/ABSOLUTE/PATH/TO/.env", "fathom-mcp-adapter"]
}
}
}Fallback
If the Fathom MCP server is down, /updateP1 falls back to the manual
"paste-me-the-transcript" mode rather than blocking (same pattern as
zendesk/vectordb).
Available Tools
4 toolsfathom_get_latest_meetingA
Read-only fetch of the single most recent Fathom meeting (the 90% case for /updateP1). Returns the same summarized fields as fathom_list_recent_meetings, for exactly one meeting.
Inputs: recorded_by.
fathom_get_transcriptA
Read-only fetch of the RAW transcript for a Fathom recording by recording_id. Returns the raw transcript text/segments — the who/what/when summary is produced by the skill, not by this tool. Get the recording_id from fathom_list_recent_meetings or fathom_get_latest_meeting.
Inputs: recording_id (required).
fathom_healthB
Read-only Fathom health/config check.
Inputs: no named parameters.
fathom_list_recent_meetingsA
Read-only list of recent Fathom meetings (newest first). Returns title, recording_id, created_at, url, share_url, and calendar_invitees for each. The Fathom API has NO title/keyword search — to find a specific meeting (e.g. 'yesterday's call with McDonald's'), list recent meetings (optionally narrowing by created_after / recorded_by) and filter the returned list by title/date/invitee yourself.
Inputs: limit, recorded_by, meeting_type, created_after, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
The tools are mostly distinct: health, list, get_latest, and transcript each serve a clear purpose. Slight overlap exists between list_recent_meetings and get_latest_meeting, but the distinction (multiple vs. single) is clear from descriptions.
All tools share the 'fathom_' prefix and most follow a verb_noun pattern (list_, get_). However, 'fathom_health' lacks an explicit verb, deviating slightly from the otherwise consistent convention.
With 4 tools, the server is well-scoped for a focused read-only meeting adapter. Each tool covers a necessary operation without redundancy or bloat.
The surface covers health, listing, latest meeting, and transcript retrieval, which are the core read operations. A minor gap is the lack of a direct 'get meeting by recording_id' endpoint, though it can be worked around via list filtering.
Related MCP Connectors
MCP server for RiverScript, an AI transcription platform - fetches transcripts shared via a link.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Related MCP Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server for accessing Fathom AI API endpoints (meetings, recordings, transcripts, summaries, teams, team members) via GET operations.62MIT
- AlicenseAqualityDmaintenanceAn MCP server for the Fathom AI meeting intelligence API520 npmMIT
- AlicenseAqualityCmaintenanceEnables Claude Desktop and MCP clients to access Fathom meeting intelligence, including listing meetings, retrieving summaries and transcripts, and searching by title.467 npmMIT
- AlicenseCqualityDmaintenanceProvides comprehensive MCP tools for Fathom.video meetings, including transcripts, summaries, action items, team management, webhooks, and analytics.14MIT