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

There is nothing to turn on — the integration is retired

Fathom is not composed into any session, and the setup path this page used to describe is gone. The fathomApiKey setting was deleted from AppSettings along with the per-session MCP composition it fed — src/shared/ipc-schemas/update-settings.ts records the removal, and src/shared/types/app-settings.ts tolerates a stale value left behind in config.json rather than reading it. There is no Settings → Channels → Fathom screen to open and no field to paste a key into.

The decisive reason is stronger than the missing key: the entry builder is no longer wired in at all. resolveFathomMcpDeps() is still exported from src/main/services/fathom/mcp-config-entry.ts, but nothing under src/ imports anything from services/fathom any more — the module survives only for its own unit test. So no session gets the Fathom tools even if a stale fathomApiKey is still sitting in config.json.

The key read inside it is a second, now-redundant gate: it does getSettings() as { fathomApiKey?: string } and returns null when none is present, and with the setting deleted that would always hold. It is belt-and-braces on a path nothing calls — not the thing keeping the integration dark.

Everything below documents the integration as it was built and how it behaved when a key was present. Treat it as a design record rather than something you can switch on today.

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 for meeting notes, and Google Meet for Meet conference records, recordings and transcripts.