Fathom MCP Server

Connect Claude to Fathom meeting recordings, transcripts, and summaries

10MITother

Install

Config snippet generator goes here (5 client tabs)

README

<div align="center">

# Fathom AI MCP Server

**Connect Claude to your Fathom meetings, transcripts, and AI summaries.**

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
[![Node.js](https://img.shields.io/badge/Node.js-18+-green.svg)](https://nodejs.org)
[![MCP](https://img.shields.io/badge/MCP-Compatible-purple.svg)](https://modelcontextprotocol.io)
[![MCP Registry](https://img.shields.io/badge/MCP_Registry-Published-green.svg)](https://registry.modelcontextprotocol.io)

[Get Started](#get-started) | [Available Tools](#available-tools) | [API Docs](https://www.fathom-mcp-server.com/docs) | [Self-Hosting](#self-hosting) | [Contributing](CONTRIBUTING.md)

[![Security](https://img.shields.io/badge/🔒_Your_data_is_100%25_secure_🔒-grey?style=flat)](#security)

</div>

---

## Get Started

This server is published to the [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.agencyenterprise/fathom-mcp-server`.

Connect in under 60 seconds:

```
https://www.fathom-mcp-server.com/mcp
```

1. Open **Claude Desktop**
2. Go to **Settings > Connectors > Add Custom Connector**
3. Paste the URL above
4. Authenticate with Fathom

That's it. Ask Claude about your meetings.

> **Organizations**: Admins must add the connector via organization admin settings, not personal settings.

## Available Tools

| Tool                | Description                                             | Docs                                                                                    |
| ------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| `list_meetings`     | List meetings with filters (date, team, recorder, etc.) | [Fathom API](https://developers.fathom.ai/api-reference/meetings/list-meetings)         |
| `search_meetings`   | Search meetings by title, host, or attendee information | [MCP Custom](#custom-mcp-tools)                                                         |
| `get_transcript`    | Get full transcript for a recording                     | [Fathom API](https://developers.fathom.ai/api-reference/recordings/get-transcript)      |
| `get_summary`       | Get AI-generated summary for a recording                | [Fathom API](https://developers.fathom.ai/api-reference/recordings/get-summary)         |
| `list_teams`        | List all accessible teams                               | [Fathom API](https://developers.fathom.ai/api-reference/teams/list-teams)               |
| `list_team_members` | List members of a team                                  | [Fathom API](https://developers.fathom.ai/api-reference/team-members/list-team-members) |

### Custom MCP Tools

#### `search_meetings`

Search Fathom meetings by title, meeting title, host name, host email, or attendee name/email. Automatically scans up to 5 pages of results. This is an MCP-native tool that performs client-side filtering since Fathom's API doesn't provide a search endpoint.

See the [Fathom MCP Server documentation](https://www.fathom-mcp-server.com/docs) for full request and response parameters.

### Example Usage in Claude

> "Show me my meetings from last week"

> "Get the transcript from my standup yesterday"

> "Summarize my meeting with the design team"

## Security

**Your Fathom data is never stored or exposed by this server.**

| Data                             | Stored? | Exposed? | Details                                                  |
| -------------------------------- | ------- | -------- | -------------------------------------------------------- |
| Meetings, transcripts, summaries | No      | No       | Fetched from Fathom and passed directly to Claude        |
| Team and member info             | No      | No       | Fetched from Fathom and passed directly to Claude        |
| OAuth tokens                     | Yes     | No       | Encrypted at rest (AES-256-GCM), never logged or exposed |

- **Pass-through architecture**: This server acts as a secure proxy, your Fathom data flows directly from Fathom to Claude without being stored, cached, or logged
- **Encryption at rest**: The only stored data (OAuth tokens) is encrypted using AES-256-GCM before being written to the database
- **HTTPS only**: All communication between Claude, this server, and Fathom is encrypted in transit

See our full [Privacy Policy](PRIVACY.md) for details on data collection, usage, and your rights.

## Permissions

This MCP server defines a custom scope called `fathom:read` for tokens it issues to Claude. This is not a Fathom API scope - it's specific to this MCP server to describe read-only access to your Fathom data.

The Fathom API itself only provides read access via its `public_api` scope. Write operations (creating/editing meetings, transcripts, etc.) are not available in the Fathom API.

## Limitations

- `search_meetings` performs client-side filtering since Fathom's API doesn't provide a search en