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

AI-generated 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.
Before you install
The FATHOM_API_KEY secret is stored in the host configuration; the optional bridge state file also holds credential data. Creating a webhook sends meeting summaries, transcripts and action items to an HTTPS URL you supply, so verify that endpoint. Webhook creation and deletion change data in your Fathom account. This is a third-party server, not the official Fathom one.

Installation

In SourceWeft

  1. Open Fathom in the dashboard and add it to a workspace.
  2. 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:

  1. list_fathom_meetings — filtered by date range, finds the meeting and returns its ID.
  2. 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 calls get_fathom_action_items directly.)

Response (trimmed):

json
{  "meeting": {    "recording_id": 123456789,    "title": "<untrusted-content source=\"fathom:meeting:title\">Q3 planning</untrusted-content>",    "scheduled_start_time": "2026-05-18T15:00:00Z",    "action_items": [      {        "description": "<untrusted-content source=\"fathom:meeting:action_item\">Lock the JD by Friday</untrusted-content>",        "completed": false,        "assignee": { "name": "<untrusted-content source=\"fathom:meeting:assignee_name\">Bob</untrusted-content>", "email": "[email protected]" }      }    ]  }}

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)
json
{  "mcpServers": {    "Fathom": {      "command": "npx",      "args": [        "-y",        "@mindstone/mcp-server-fathom"      ],      "env": {        "FATHOM_API_KEY": ""      }    }  }}

Quick Start

Install & build

bash
cd <path-to-repo>/connectors/fathomnpm installnpm run build

npx (once published)

bash
npx -y @mindstone/mcp-server-fathom

Local

bash
node dist/index.js

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 management
  • MINDSTONE_REBEL_BRIDGE_STATE — backwards-compatible alias for MCP_HOST_BRIDGE_STATE

Host configuration examples

Claude Desktop / Cursor

json
{  "mcpServers": {    "Fathom": {      "command": "npx",      "args": ["-y", "@mindstone/mcp-server-fathom"],      "env": {        "FATHOM_API_KEY": "your-api-key"      }    }  }}

Local development (no npm publish needed)

json
{  "mcpServers": {    "Fathom": {      "command": "node",      "args": ["<path-to-repo>/connectors/fathom/dist/index.js"],      "env": {        "FATHOM_API_KEY": "your-api-key"      }    }  }}

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 items
  • get_fathom_transcript — Get the transcript for a meeting
  • get_fathom_meeting_participants — List the participants of a meeting
  • get_fathom_action_items — List action items across meetings (open items by default)

Recordings

  • request_fathom_recording_download — Start async generation of a downloadable recording file
  • get_fathom_recording_download_status — Poll a download for its short-lived signed URL

Teams

  • list_fathom_teams — List all accessible teams
  • list_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 control
  • delete_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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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