Fathom
ai.fathom.apiPublished by api.fathom.aiOfficial publisherv1.0.0Updated Oct 30, 2026
Give your AI assistant real meeting context via Fathom so every output grounded in your work
Overview
Remote Fathom MCP endpoint that gives an AI assistant meeting context from your Fathom recordings so its output is grounded in your work.
- What you can do
- Connects the assistant to your Fathom meeting data through a hosted endpoint.
- Supplies meeting context so answers and generated output can be grounded in your recorded conversations.
- No individual tools are documented in the manifest, so the exact actions available are not specified.
- When to use it
- Useful when you want an assistant to work from your Fathom meeting recordings and notes rather than generic knowledge, for example when drafting follow-ups or summaries tied to real conversations.
- Requirements
- A remote MCP endpoint at api.fathom.ai over streamable HTTP; OAuth authentication is required, so a Fathom account that can authorize the connection is needed. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Fathom in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.fathom.api%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"fathom": {
"type": "http",
"url": "https://api.fathom.ai/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
Other Fathom integrations
Fathom (lab)
dev.fly.fathom-lab-doorOfficial publisher
A remote lab server for exploring places and groups tied to an interest in a town, with sources, and proposing missing knowledge types, views and extensions.
Eclipse Fathom MCP
Published by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLC
DeFi, measured honestly: signed protocol registry, dual-source risk reads, and an allowance audit
Fathom
ai.qompass
Reverse-engineering tools for agents over MCP/A2A, with evidence-carrying findings.
MailFathom
Published by GitHub account fathomise
Self-hosted email archive that syncs IMAP mail into your own PostgreSQL database and serves it to AI agents for search, cited answers, drafting and sending.
Fathoms to meters
Published by GitHub account sadri-dridi
A remote MCP endpoint of small utility tools: unit conversion, time, URL and text shape checks, plus link-out indexes to third-party services.