Fathom

Fathom

Official

Official Fathom remote MCP — access meeting recordings, transcripts, summaries, and webhooks from any MCP client.

Score 54(?)FathomProprietaryVerified Top MCPs for Meetings & Notes →

Quick answer

What it does

Exposes Fathom's recording, transcript, summary, team, and webhook APIs as MCP tools — search past meetings, pull a transcript, summarize a call, or list webhook subscriptions.

Best for

  • Sales call recall
  • Customer-success meeting summaries
  • Cross-call pattern search
  • Webhook-driven post-meeting automation

Not for

  • Teams not on Fathom
  • Live in-call assistance

Source: top-mcps.com/mcp/fathom — verified Aug 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "fathom": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://api.fathom.ai/mcp"
          ]
        }
      }
    }

    Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://api.fathom.ai/mcp. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI or .mcp.json
    claude mcp add --transport http fathom https://api.fathom.ai/mcp

    Then run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

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

    Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

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

    VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "fathom": {
          "serverUrl": "https://api.fathom.ai/mcp"
        }
      }
    }

    Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "fathom": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://api.fathom.ai/mcp"
          ]
        }
      }
    }

    Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "streamable-http",
              "url": "https://api.fathom.ai/mcp"
            }
          }
        ]
      }
    }

    Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI
    codex mcp add fathom --url https://api.fathom.ai/mcp

    Codex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "fathom": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://api.fathom.ai/mcp"
            ]
          }
        }
      }
    }

    Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ChatGPT → Settings → Connectors (remote URL)
    {
      "name": "Fathom",
      "transport": "http",
      "url": "https://api.fathom.ai/mcp"
    }

    Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Summarize every customer call from this week

    Using Fathom, list every customer call I had this week. For each call return: title, customer, date, and a three-bullet summary highlighting any product-feedback or pricing topics.

    Tested with: Claude Desktop, Cursor.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Read + write
Sandbox
Hosted by Fathom. OAuth-scoped to the connecting user. Read on recordings/transcripts/summaries; write only on webhook configuration.
Gotchas
  • Webhook configuration is a write surface — restrict the OAuth scope if the agent should only read.
  • Transcript retrieval respects per-recording permissions; private recordings stay private.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. meetings & notes work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-meeting-notes
Compare Fathom against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Fathom MCP vs [Fellow MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/fathom
- top-mcps.com listing for Fellow
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Fathom MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/fathom (fetch https://top-mcps.com/mcp/fathom.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Meetings & Notes MCPs

Other tools in the same category worth evaluating.

Fellow
Official

Anthropic-verified Fellow Connector — query meeting notes, transcripts, action items, and calendar events from Claude.

fellow, meeting-notes, transcripts, action-items
< 1 minLow
Fireflies.ai
Official

Official Fireflies remote MCP — query meeting transcripts, AI summaries, and action items via OAuth or API key.

fireflies, meeting-notes, transcripts, ai-summaries
2 minLow

Compared with Fathom

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Meetings & Notes? See all Meetings & Notes MCPs →