Fathom MCP server

Fathom × VS Code

Use the Fathom MCP server
in VS Code

Search your Fathom meeting recordings, transcripts, and summaries — straight from your AI. This guide connects Fathom to VS Code (GitHub Copilot's agent mode) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · OAuth sign-in

Setup: Fathom in VS Code

VS Code adds MCP servers via MCP server configuration. The gateway route takes about two minutes:

  1. Connect Fathom to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to VS Code' — VS Code prompts to add the gateway as an HTTP MCP server.
  3. Confirm and approve the sign-in.
  4. Copilot's agent mode can now use Fathom — logged and governed through your gateway.

What to ask once it’s connected

Summarize my last meeting and list the action items.
What did we decide about pricing in yesterday's call?
Draft a follow-up email from this meeting's transcript.
Find every meeting where we discussed the Q3 roadmap.

Why route it through a gateway

One URL, every client

The same Fathom connection works in Claude, Claude Code, ChatGPT, Cursor too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Fathom exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything VS Code did with Fathom — searchable, exportable, auditable.

Scanned and probed

Fathom passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Fathom in Claude · Fathom in Claude Code · Fathom in ChatGPT · Fathom in Cursor