Fathom MCP Server

by fathom-api Your server? Claim it

answering

Fathom is answering right now. Last checked 14 min ago.

Give your AI assistant real meeting context via Fathom so every output grounded in your work

Uptime history 51 days of history · worst day 81%

51 days agonow

92.3%

Uptime 24h

84 of 91 checks

—

Tools

hidden behind auth

200 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Fathom does not always answer

Over the last week it answered 95.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://api.fathom.ai/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://api.fathom.ai/mcp	streamable-http	sign-in	194 ms	14 min ago

Alternatives to Fathom

same job, measured the same way

Coach MCP

by iamcoach

Your endurance training data in your AI assistant: activities, recovery, plan, workout edits.

answering

Realevents

by ykastelnik

Create and manage events in seconds from your AI assistant. No account needed.

91 installs/wk local only

Cachetank MCP

by jacobsilver7-art

CacheTank MCP server gives every AI tool your personal context so you never start from zero.

28 installs/wk local only

Reel Estate MCP

by tryreelestate

Turn real-estate listing photos into property videos from your AI assistant.

local only

Mailopoly

by mailopoly

Your unified inbox — everything that reaches you, understood and actionable from your AI assistant.

answering

Speak AI

by speakai

Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.

159 installs/wk answering

Memo AI – meeting assistant

by memoai

Search transcripts and summaries of your meetings, calls, and recordings in Memo AI

28 installs/wk local only

Delimit

by delimit-ai

One workspace for every AI coding assistant. Shared tasks, memory, and governance.

local only

Fathom — questions

Answers built from our own checks of this server.

Why is there no tool list for Fathom?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 92.3% of checks in the last 24 hours got a reply.

Is Fathom working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 84 of 91 checks got a reply (92.3%), average response time 200 ms. The bar chart above shows every period we have measured.

How do I connect Fathom?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Fathom?

No API key is involved. Fathom answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Fathom?

It answers our handshake in 200 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.