Fathom

io.github.mindstone由 GitHub 账号 mindstone 发布v0.3.0更新于 Oct 24, 2026

Fathom AI meeting transcription MCP server for Model Context Protocol hosts

发布方自己的服务:Fathom

已验证STDIO仅桌面效率与工作流沟通与协作

概览

AI 生成的概览

本地 MCP 服务器,让助手列出和搜索 Fathom AI 会议、读取转录、跟踪行动项,并管理团队与 Webhook。

可以做什么
列出和搜索会议,获取单个会议的详情、摘要、参与者和行动项,包括跨会议的未完成事项。读取会议转录文本。发起并轮询录音下载,获取短期有效的签名链接。列出团队及其成员。创建和删除 Webhook,将新会议数据推送到 HTTPS 地址。在宿主内配置 Fathom API 密钥。
适用场景
当会议记录、转录和后续行动项存放在 Fathom 中,希望助手在对话内直接提取它们用于摘要、任务清单或跨会议回顾时适用。
运行要求
通过 npx 以 stdio 在本地运行,需要 Node.js 20+ 和 npm。需要 Fathom API 密钥,放在 FATHOM_API_KEY 环境变量中。可选 MCP_HOST_BRIDGE_STATE 路径(别名 MINDSTONE_REBEL_BRIDGE_STATE)指向用于凭据管理的宿主桥接状态文件。需要访问 Fathom API 的网络连接。
安装前请注意
FATHOM_API_KEY 密钥保存在宿主配置中;可选的桥接状态文件也包含凭据数据。创建 Webhook 会把会议摘要、转录和行动项发送到你提供的 HTTPS 地址,请确认该端点可信。创建和删除 Webhook 会改动 Fathom 账户中的数据。这是第三方服务器,并非 Fathom 官方服务器。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Fathom,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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.

来源:connectors/fathom/README.md,提交 22c4611

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.3.0最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。

其他 Fathom 集成