
Fathom
io.github.mindstonePublished by GitHub account mindstonev0.3.0Updated Oct 24, 2026
Fathom AI meeting transcription MCP server for Model Context Protocol hosts
The publisher's own server: Fathom
Overview
Local MCP server that lets an assistant list and search Fathom AI meetings, read transcripts, track action items, and manage teams and webhooks.
- What you can do
- List and search meetings, and fetch a meeting's details, summary, participants and action items, including open items across meetings. Read meeting transcripts. Request and poll recording downloads for short-lived signed links. List teams and their members. Create and delete webhooks that push new-meeting data to an HTTPS URL. Configure the Fathom API key from within the host.
- When to use it
- Useful when meeting notes, transcripts and follow-up action items live in Fathom and you want an assistant to pull them into summaries, task lists or cross-meeting reviews without leaving the chat.
- Requirements
- Runs locally over stdio via npx, so Node.js 20+ and npm are needed. A Fathom API key is required in the FATHOM_API_KEY environment variable. An optional MCP_HOST_BRIDGE_STATE path (alias MINDSTONE_REBEL_BRIDGE_STATE) can point to a host bridge state file for credential management. Network access to the Fathom API.
Installation
In SourceWeft
- Open Fathom in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@mindstone/mcp-server-fathom
[npm version] [License: FSL-1.1-MIT]
List and search meetings, view details, read transcripts, and manage teams via Fathom AI.
Local-only Fathom MCP. Not the official server — built before Fathom shipped theirs; tokens stay on disk and each release goes through our own security review.
Status
- Version: 0.3.0 · npm
- Auth: API key (
FATHOM_API_KEY) - Tools: 12 (meetings, transcripts, action items, recordings, teams, webhooks)
- Surface: cloud-api
- Machine-readable:
STATUS.json
Why this exists
When we built this in early 2026, Fathom had not published an official MCP server, and the community options available at the time were thin and unmaintained — they listed meetings, but did not cover the team and transcript data our meeting-notes workflows depend on. We wrote our own so that any MCP host could pull Fathom transcripts and meeting details with the same credential handling, timeouts, and safety wrapping we apply across the rest of this repository. Fathom has since released an official MCP server; we continue to maintain this one because it runs locally on the user's machine and goes through our own security review before each release.
Example interaction
"Pull yesterday's Q3 planning meeting from Fathom and list the action items from the transcript."
Tools the host calls:
list_fathom_meetings— filtered by date range, finds the meeting and returns its ID.get_fathom_meeting— fetches details, summary, and action items for that meeting ID. (For a cross-meeting view — "what are my open action items from customer calls this week?" — the host callsget_fathom_action_itemsdirectly.)
Response (trimmed):
Requirements
- Node.js 20+
- npm
One-click install
[Add to Cursor] [Add to VS Code] [Add to VS Code Insiders]
After clicking the button, your host will prompt you to fill: FATHOM_API_KEY.
Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Fathom)
Quick Start
Install & build
npx (once published)
Local
Configuration
Environment variables
FATHOM_API_KEY— Fathom API key (from fathom.video settings)MCP_HOST_BRIDGE_STATE— optional path to a host bridge state file used for credential managementMINDSTONE_REBEL_BRIDGE_STATE— backwards-compatible alias forMCP_HOST_BRIDGE_STATE
Host configuration examples
Claude Desktop / Cursor
Local development (no npm publish needed)
Tools (12)
Configuration
configure_fathom_api_key— Configure the Fathom API key
Meetings
list_fathom_meetings— List meetings with server-side filtering (optionally including action items)get_fathom_meeting— Get details for a single meeting, including summary and action itemsget_fathom_transcript— Get the transcript for a meetingget_fathom_meeting_participants— List the participants of a meetingget_fathom_action_items— List action items across meetings (open items by default)
Recordings
request_fathom_recording_download— Start async generation of a downloadable recording fileget_fathom_recording_download_status— Poll a download for its short-lived signed URL
Teams
list_fathom_teams— List all accessible teamslist_fathom_team_members— List members of a specific team
Webhooks
create_fathom_webhook— Push new-meeting data (summary, transcript, action items) to an HTTPS URL you controldelete_fathom_webhook— Delete a webhook by id
All caller-controllable text returned by these tools (meeting titles, attendee
names, AI summaries, transcript lines, action item descriptions, team names) is
wrapped in <untrusted-content> envelopes so the host treats meeting content as
data, not instructions. The same applies to vendor API error bodies surfaced in
tool errors, which are additionally truncated.
Licence
FSL-1.1-MIT — Functional Source License, Version 1.1, with MIT future licence. The software converts to MIT licence on 2030-04-08.
Source: connectors/fathom/README.md at commit 22c4611
Tools
0Version history
1- v0.3.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Fathom integrations
Fathom
ai.fathom.apiOfficial publisher
Remote Fathom MCP endpoint that gives an AI assistant meeting context from your Fathom recordings so its output is grounded in your work.
Fathom (lab)
dev.fly.fathom-lab-doorOfficial publisher
A remote lab server for exploring places and groups tied to an interest in a town, with sources, and proposing missing knowledge types, views and extensions.

Eclipse Fathom MCP
Published by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLC
DeFi, measured honestly: signed protocol registry, dual-source risk reads, and an allowance audit

Fathom
ai.qompass
Reverse-engineering tools for agents over MCP/A2A, with evidence-carrying findings.

MailFathom
Published by GitHub account fathomise
Self-hosted email archive that syncs IMAP mail into your own PostgreSQL database and serves it to AI agents for search, cited answers, drafting and sending.