# Fathom MCP server

> Bring Fathom meeting recordings, transcripts and summaries into your AI assistant as context for its answers.

- Listing: https://mcp.tc/i/fathom
- Connect: use the server's own URL `https://api.fathom.ai/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Communication & Meetings](https://mcp.tc/c/communication)
- Vendor: Fathom
- Homepage: <https://www.fathom.ai/>

## About

Connects an AI assistant to Fathom, the AI meeting notetaker. It gives the assistant access to meeting context such as recordings, transcripts and summaries, so its output can be grounded in what was discussed in your meetings.

Runs as a hosted streamable HTTP endpoint at https://api.fathom.ai/mcp. Users sign in to their Fathom account through OAuth. No local install or API key is needed. The tool list is not published ahead of sign-in.

## What it can do

- Pull meeting context from Fathom into the assistant
- Read meeting transcripts
- Read meeting summaries
- Ground answers and drafts in your real meetings

## Example prompts

- "Summarize my last Fathom meeting with the design team"
- "What action items came out of yesterday's customer call?"
- "Find where pricing was discussed in my recent meetings"
- "Draft a follow-up email based on my latest Fathom recording"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http fathom https://api.fathom.ai/mcp
```

2. Start Claude Code, type `/mcp`, pick **fathom** and choose **Authenticate**. A browser window opens for the Fathom sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Fathom** and paste this URL:

```url
https://api.fathom.ai/mcp
```

3. Click **Add**, then **Connect**, and sign in when Fathom asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Fathom&connectorUrl=https%3A%2F%2Fapi.fathom.ai%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://api.fathom.ai/mcp` and click **Add**.

3. Click **Connect** and sign in when Fathom asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://api.fathom.ai/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Fathom to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=fathom&config=eyJ1cmwiOiJodHRwczovL2FwaS5mYXRob20uYWkvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "fathom": {
      "url": "https://api.fathom.ai/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=fathom&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.fathom.ai%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"fathom","type":"http","url":"https://api.fathom.ai/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "fathom": {
      "type": "http",
      "url": "https://api.fathom.ai/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "fathom": {
      "serverUrl": "https://api.fathom.ai/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add fathom --url https://api.fathom.ai/mcp
codex mcp login fathom
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.fathom]
url = "https://api.fathom.ai/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http fathom https://api.fathom.ai/mcp
```

Then, inside Gemini CLI, run `/mcp auth fathom` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "fathom": {
      "type": "http",
      "url": "https://api.fathom.ai/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.fathom.ai/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/fathom (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report