Fathom
MCP-Server von Fathom
Bring Fathom meeting recordings, transcripts and summaries into your AI assistant as context for its answers.
Mit Fathom verbinden
Fathom braucht eine Anmeldung. Verbinde dich mit seiner eigenen URL:
Dein Client öffnet beim ersten Mal die Anmeldung von Fathom. Das Token bleibt zwischen deinem Client und Fathom.
Diesen Server teilen
Öffnet diese Seite, mit der URL und den Einrichtungsschritten.
mcp.tc/i/fathomÜber den Server
Connects an AI assistant to Fathom, the AI meeting notetaker. It gives the assistant access to meeting context such as recordings, transcripts and summaries, so its output can be grounded in what was discussed in your meetings.
Runs as a hosted streamable HTTP endpoint at https://api.fathom.ai/mcp. Users sign in to their Fathom account through OAuth. No local install or API key is needed. The tool list is not published ahead of sign-in.
Was du damit machen kannst
- Pull meeting context from Fathom into the assistant
- Read meeting transcripts
- Read meeting summaries
- Ground answers and drafts in your real meetings
Tools
Fathom zeigt seine Tools erst nach der Anmeldung, deshalb können wir sie hier nicht auflisten. Dein Client zeigt sie, sobald du verbunden bist.
Beispiel-Prompts
Summarize my last Fathom meeting with the design team
What action items came out of yesterday's customer call?
Find where pricing was discussed in my recent meetings
Draft a follow-up email based on my latest Fathom recording
Einrichtung
Jeder Client verbindet sich mit api.fathom.ai, und beim ersten Mal fragt Fathom nach deiner Anmeldung. Wähl deinen; die Seite merkt sich deine Wahl.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http fathom https://api.fathom.ai/mcp- Start Claude Code, type
/mcp, pick fathom and choose Authenticate. A browser window opens for the Fathom sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it Fathom and paste this URL:
https://api.fathom.ai/mcp- Click Add, then Connect, and sign in when Fathom asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Zu claude.ai hinzufügen (öffnet in einem neuen Tab)
- Check that the URL reads
https://api.fathom.ai/mcpand click Add. - Click Connect and sign in when Fathom asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://api.fathom.ai/mcpas the server URL and choose OAuth. ChatGPT sends you to Fathom to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
Cursor
Zu Cursor hinzufügen (öffnet in einem neuen Tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"fathom": {
"url": "https://api.fathom.ai/mcp"
}
}
}Cursor shows Needs login next to the server. Click it to sign in.
VS Code
Install in VS Code (öffnet in einem neuen Tab)
Or from a terminal:
code --add-mcp '{"name":"fathom","type":"http","url":"https://api.fathom.ai/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"fathom": {
"type": "http",
"url": "https://api.fathom.ai/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"fathom": {
"serverUrl": "https://api.fathom.ai/mcp"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add fathom --url https://api.fathom.ai/mcp
codex mcp login fathomOr edit ~/.codex/config.toml directly:
[mcp_servers.fathom]
url = "https://api.fathom.ai/mcp"Gemini CLI
gemini mcp add --transport http fathom https://api.fathom.ai/mcpThen, inside Gemini CLI, run /mcp auth fathom to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"fathom": {
"type": "http",
"url": "https://api.fathom.ai/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://api.fathom.ai/mcp.
Häufige Fragen
Can I paste mcp.tc/i/fathom into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://api.fathom.ai/mcp, so your client talks to Fathom directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Fathom need an API key or a sign-in?
Yes, you need a Fathom account. The first time your client connects, it opens Fathom’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is Fathom a remote or a local server?
Remote. Fathom hosts it at https://api.fathom.ai/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Fathom do?
You can Pull meeting context from Fathom into the assistant, Read meeting transcripts und Read meeting summaries.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc’s robot read Fathom’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Einbinden
Zeig Fathom in einem README oder auf deiner Website. Jede Einbindung verlinkt auf diese Seite, nutzt die eigene URL des Servers und setzt keine Cookies. So funktionieren Einbindungen
README-Badge
[](https://mcp.tc/i/fathom)<a href="https://mcp.tc/i/fathom"><img src="https://mcp.tc/i/fathom/badge.svg" alt="Fathom on mcp.tc" height="20"></a>Es folgt dem hellen oder dunklen Modus der Lesenden. Hänge ?theme=light oder ?theme=dark an, um ihn festzulegen, oder ?style=compact, um das Zeichen ohne Schriftzug zu zeigen.
Website-Karte
<script src="https://mcp.tc/w/fathom.js" async></script>Die Karte erscheint dort, wo das Tag steht. Füge dem Tag data-theme="dark" oder data-size="compact" hinzu, um sie zu ändern. Die Datei enthält alles, was sie braucht, stellt also keine weiteren Anfragen und setzt keine Cookies.
iframe
<iframe src="https://mcp.tc/embed/fathom" title="Fathom on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Nutze es auf Seiten, die keine Skripte erlauben. Hänge ?theme=light oder ?theme=dark an die Adresse an, um die Farben festzulegen.
JSON
Der Eintrag als Daten für deine eigenen Seiten und Tools: Name, Kurzbeschreibung, die eigene URL des Servers, Tools und die „Add to“-Links. Jede Website kann ihn lesen (CORS ist offen).
https://mcp.tc/i/fathom.jsonmcp.tc ist nicht mit Fathom verbunden. Diese Seite entstand aus den öffentlichen Metadaten von Fathom, zuletzt geprüft am 3. Okt. 2026, und ein KI-Modell hat die Beschreibung geschrieben, sie kann also Fehler enthalten. Namen und Marken gehören ihren Inhabern. Stimmt etwas nicht? Eintrag melden.