# Fathom: MCP server status, API access gate and what it does

> Free AI meeting recorder/notetaker that transcribes calls and generates summaries, action items, and CRM sync. Official MCP, Free to start. Checked 2026-09-02.

*Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).*

*Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.*

---
[Directory](../index.md) /
[Conversation Intel](../categories/conversation-intel.md) /
Fathom

# Fathom

[Official MCP](../mcp/official.md)
[Free to start](../gates/free.md)
[Conversation Intel](../categories/conversation-intel.md)
RESEARCHED
Checked 2026-09-02

> **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: [fathom.video](https://fathom.video) · entry id 03-fathom · source 03-conversation-intel.md line 182

**What it does**
Free AI meeting recorder/notetaker that transcribes calls and generates summaries, action items, and CRM sync.

**AI features, separated from automation with an AI label on it**
AI-generated meeting summaries and highlights, action-item extraction; the free plan caps advanced AI summaries at the first 5 calls/month.

**RevOps role**
Low-friction meeting-capture layer, notable in this category for a genuinely open, no-paywall API.

**MCP server**

- **Status bucket**: Official MCP

- **Auth**: In-client authorization: the docs say to add the server URL "then authenticate to access your meeting data", via the Fathom connector in Claude (Connect, then complete the authorization prompts) or "claude mcp add fathom -- npx mcp-remote@latest https://api.fathom.ai/mcp" in Claude Code; the docs do not name the mechanism (OAuth vs key). Community servers use a Fathom API key (FATHOM_API_KEY environment variable).

- **Parsed URLs**: 5 found in the mcp_url field

- **Endpoint probe**: docs page, not an endpoint
- **Docs URL**: [https://developers.fathom.ai/mcp-docs](https://developers.fathom.ai/mcp-docs)
- **Probed**: 2026-09-04, HTTP 200

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-02. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://developers.fathom.ai/mcp-docs (first-party docs; server endpoint https://api.fathom.ai/mcp, registry entry ai.fathom.api/mcp. Community alternatives: https://github.com/trevorwelch/fathom-video-mcp ; https://github.com/lukas-bekr/fathom-mcp ; https://github.com/druellan/Fathom-Simple-MCP)

- [https://developers.fathom.ai/mcp-docs](https://developers.fathom.ai/mcp-docs)
- [https://api.fathom.ai/mcp](https://api.fathom.ai/mcp)
- [https://github.com/trevorwelch/fathom-video-mcp](https://github.com/trevorwelch/fathom-video-mcp)
- [https://github.com/lukas-bekr/fathom-mcp](https://github.com/lukas-bekr/fathom-mcp)
- [https://github.com/druellan/Fathom-Simple-MCP](https://github.com/druellan/Fathom-Simple-MCP)

**What this server exposes**

Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the [tools index](../tools-index.md).

**Command line**

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

**Access gate**

- **Gate bucket**: Free to start

- **Can a solo operator reach it**: Yes, without talking to anyone

api_gate, verbatim from the file:

free. API access is included on all plan tiers including Free, with public developer docs and a downloadable OpenAPI spec - you can generate a key and start calling the API without upgrading. No published enterprise-only API tier.

**API documentation**

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

**GitHub health**

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

- [https://github.com/druellan/Fathom-Simple-MCP](https://github.com/druellan/Fathom-Simple-MCP)
- [https://github.com/lukas-bekr/fathom-mcp](https://github.com/lukas-bekr/fathom-mcp)
- [https://github.com/trevorwelch/fathom-video-mcp](https://github.com/trevorwelch/fathom-video-mcp)

**On GitHub**

No GitHub organisation could be tied to fathom.video with evidence on 2026-09-08.

Recorded by the harvest: github candidates were seen but none passed the evidence rules.

8 candidate accounts seen and rejected by the evidence rules: trevorwelch, lukas-bekr, druellan, fathomnet, fathom-global. A name match alone is never accepted; the account has to point at the vendor domain.

**Jobs it can do**

- [Fetch a call transcript](../jobs/fetch-call-transcript.md)
- [Summarize a meeting](../jobs/summarize-meeting.md)
- [Write CRM records](../jobs/write-crm-records.md)

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

**Sources**

- [https://pipeline.zoominfo.com/sales/fathom-api-review](https://pipeline.zoominfo.com/sales/fathom-api-review)
- [https://www.fathom.ai/pricing](https://www.fathom.ai/pricing)
- [https://github.com/trevorwelch/fathom-video-mcp](https://github.com/trevorwelch/fathom-video-mcp)
- [https://github.com/lukas-bekr/fathom-mcp](https://github.com/lukas-bekr/fathom-mcp)
- [https://developers.fathom.ai/mcp-docs](https://developers.fathom.ai/mcp-docs)
- [https://developers.fathom.ai/mcp-docs/claude](https://developers.fathom.ai/mcp-docs/claude)
- [https://registry.modelcontextprotocol.io/v0/servers?search=fathom](https://registry.modelcontextprotocol.io/v0/servers?search=fathom)

7 source URLs. Raw sources field, verbatim:

https://pipeline.zoominfo.com/sales/fathom-api-review, https://www.fathom.ai/pricing, https://github.com/trevorwelch/fathom-video-mcp, https://github.com/lukas-bekr/fathom-mcp, https://developers.fathom.ai/mcp-docs, https://developers.fathom.ai/mcp-docs/claude, https://registry.modelcontextprotocol.io/v0/servers?search=fathom

**Notes, verbatim from the file**
Another Fireflies-style contrast case: free API access, but no official MCP server yet - only community wrappers. 2026-09-02: mcp_status community -> official. Fathom's own developer docs at https://developers.fathom.ai/mcp-docs state "Fathom now offers an official MCP (Model Context Protocol) server" with the endpoint https://api.fathom.ai/mcp (answered 200 today), and the official MCP registry lists it as ai.fathom.api/mcp with that remote. The "no official MCP server yet" sentence above is superseded; the three community wrappers remain as alternatives.

**Provenance**

- **Entry id**: 03-fathom

- **Source file**: 03-conversation-intel.md

- **Source line**: 182

- **Tier**: RESEARCHED

- **last_checked**: 2026-09-02

- **Data baked**: 2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).
