---
title: Fathom (meeting transcripts via MCP)
---

# Fathom (meeting transcripts via MCP)

## What it is

Built-in MCP integration that gives your Claude sessions read-only access to your
**Fathom.ai** meeting recordings. Sessions can list recent meetings, search by
keyword, read full speaker-labeled transcripts, and view AI-generated summaries —
all from within a conversation.

Fathom is a meeting-recording and note-taking app. Omniscio wraps its public REST API
in a local stdio MCP server that runs alongside each session. Read-only — it
never edits or deletes anything in Fathom.

## Where to find it

### How to turn it on

1. Open **Settings → Channels → Fathom**.
2. Enable the **Fathom Integration** toggle.
3. Paste your Fathom API key (generate one in Fathom → User Settings → API
   Access).
4. New sessions now have five Fathom tools available automatically.

## How it behaves

### What sessions can do

- **List meetings** — paginated list of recent meetings (title, date, duration).
- **Search meetings** — find meetings by keyword in the title or content.
- **Read a transcript** — full speaker-labeled transcript of any meeting.
- **View a summary** — AI-generated summary from Fathom.
- **List teams** — see which teams are available in your Fathom account.

### Rate limits

Fathom's API allows 60 requests per minute. If you hit the limit, the server
returns a descriptive error and the agent can retry after a brief wait.

### Per-session control

Like all built-in MCPs, Fathom respects the 3-layer MCP selection resolver:
session override → project default → global default. You can disable it for a
specific session or project without turning it off globally.

See the contract `.claude/memory/contracts/fathom-mcp-contract.md` for the
load-bearing invariants and the tests that lock them.

## For agents

### Auth & security

- Your API key is stored **encrypted at rest** (via Electron `safeStorage`). It
  never crosses IPC to the renderer.
- The key is fetched at call time via the credential-proxy loopback
  (`POST /mcp/credential`); it is NOT written into the `.mcp.json` env.
- Fathom is **force-disabled** for Search and Ask Omniscio sessions. It is
  **allowed** in KMS (Vault) sessions because the credential-proxy model
  keeps the API key out of the on-disk config.

## Related

Other meeting and transcript sources in this library: [Granola](granola.md) for meeting notes, and [Google Meet](google-meet.md) for Meet conference records, recordings and transcripts.