# Fathom

Connect an AI host to Fathom meeting data to find calls, read transcripts, and retrieve action items. Setup requires a Fathom API key.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 13
- Author: mindstone
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/mindstone/mcp-servers/tree/HEAD/connectors/fathom
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/mcp/fathom

## What it does

Fathom gives an MCP host access to meeting data through the Fathom API. The server can search meetings by date range, retrieve a meeting’s details and transcript, list participants, and gather action items across calls. It also includes tools for teams and webhooks, plus a way to request a recording download and check its status.

It runs locally with `npx`. You’ll need Node.js 20+, npm, and a Fathom API key set as `FATHOM_API_KEY`. For Claude Code, add the server with the command below and supply your key. Without a valid key, the server cannot access Fathom data.

Text returned from meetings, including transcript lines and titles, is marked as untrusted so the host treats it as data rather than instructions. This is a locally run community server; Fathom also has an official MCP server.

## Requirements
- Needs: Node.js (commands run via npx)
- Environment variables: `FATHOM_API_KEY`, `MCP_HOST_BRIDGE_STATE`, `MINDSTONE_REBEL_BRIDGE_STATE` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env FATHOM_API_KEY=<FATHOM_API_KEY> --env MCP_HOST_BRIDGE_STATE=<MCP_HOST_BRIDGE_STATE> --env MINDSTONE_REBEL_BRIDGE_STATE=<MINDSTONE_REBEL_BRIDGE_STATE> --transport stdio fathom -- npx -y @mindstone/mcp-server-fathom
```
Replace <…> with your own values

### Codex

**Platform CLI**
```bash
codex mcp add fathom --env FATHOM_API_KEY=<FATHOM_API_KEY> --env MCP_HOST_BRIDGE_STATE=<MCP_HOST_BRIDGE_STATE> --env MINDSTONE_REBEL_BRIDGE_STATE=<MINDSTONE_REBEL_BRIDGE_STATE> -- npx -y @mindstone/mcp-server-fathom
```
Replace <…> with your own values

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "fathom": {
            "command": "npx",
            "args": [
                "-y",
                "@mindstone/mcp-server-fathom"
            ],
            "env": {
                "FATHOM_API_KEY": "<FATHOM_API_KEY>",
                "MCP_HOST_BRIDGE_STATE": "<MCP_HOST_BRIDGE_STATE>",
                "MINDSTONE_REBEL_BRIDGE_STATE": "<MINDSTONE_REBEL_BRIDGE_STATE>"
            }
        }
    }
}
```
Replace <…> with your own values

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "fathom": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@mindstone/mcp-server-fathom"
            ],
            "env": {
                "FATHOM_API_KEY": "<FATHOM_API_KEY>",
                "MCP_HOST_BRIDGE_STATE": "<MCP_HOST_BRIDGE_STATE>",
                "MINDSTONE_REBEL_BRIDGE_STATE": "<MINDSTONE_REBEL_BRIDGE_STATE>"
            }
        }
    }
}
```
Replace <…> with your own values

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e FATHOM_API_KEY=<FATHOM_API_KEY> -e MCP_HOST_BRIDGE_STATE=<MCP_HOST_BRIDGE_STATE> -e MINDSTONE_REBEL_BRIDGE_STATE=<MINDSTONE_REBEL_BRIDGE_STATE> fathom npx -y @mindstone/mcp-server-fathom
```
Replace <…> with your own values

## When to use it
- find Fathom meetings within a date range
- retrieve a meeting transcript and summary
- collect open action items across meetings
- list members of a Fathom team
- send new-meeting details to an HTTPS webhook

## Example prompts
- Find my Fathom meetings from last week and read the transcript for the selected call.
- Gather open action items from my Fathom meetings.
- List the members of my Fathom team and create a webhook for new meetings at my HTTPS endpoint.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 392262
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33989
- [World Monitor](https://affpapa.org/en/nevibecode/mcp/world-monitor.md) — MCP server · ★ 89609
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81163
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74569
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89899

## Other versions with the same name
- [Fathom · qompassai](https://affpapa.org/en/nevibecode/mcp/qompassai-fathom.md)

From the same set: [mindstone/mcp-servers](https://affpapa.org/en/nevibecode/by/mindstone/mcp-servers.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md