FathomBridge
# š FathomBridge
> Your meetings, in your AI.
**FathomBridge** is a zero-install MCP (Model Context Protocol) server
that connects any AI CLI or IDE directly to your Fathom meeting
transcripts, summaries, and action items ā using your API key.
No cloning. No building. One line of config.
[](https://www.npmjs.com/package/fathombridge)
[](https://opensource.org/licenses/MIT)
[](https://modelcontextprotocol.io)
---
## ⨠Features
- š **List meetings** ā with date, team, and pagination filters
- š **Full transcripts** ā speaker-labelled with timestamps
- š¤ **AI summaries** ā key points and decisions
- ā
**Action items** ā with owners and due dates
- š **Smart search** ā find any meeting by title, host, or participant
- š„ **Teams** ā list your Fathom organization teams
- ā” **Zero install** ā runs via npx, nothing to clone or build
- š **API key auth** ā simple, local, no OAuth flow needed
---
## š Quick Start
### Step 1 ā Get Your Fathom API Key
1. Log in to [fathom.video](https://fathom.video)
2. Go to **Settings ā Integrations ā API**
3. Copy your API key
### Step 2 ā Add to Your AI Tool Config
**Claude Code** (`~/.claude/claude.json`):
```json
{
"mcpServers": {
"fathom": {
"command": "npx",
"args": ["-y", "fathombridge"],
"env": {
"FATHOM_API_KEY": "your-api-key-here"
}
}
}
}
```
**Cursor** (`.cursor/mcp.json`):
```json
{
"mcpServers": {
"fathom": {
"command": "npx",
"args": ["-y", "fathombridge"],
"env": {
"FATHOM_API_KEY": "your-api-key-here"
}
}
}
}
```
**Windsurf** (`~/.codeium/windsurf/mcp_config.json`):
```json
{
"mcpServers": {
"fathom": {
"command": "npx",
"args": ["-y", "fathombridge"],
"env": {
"FATHOM_API_KEY": "your-api-key-here"
}
}
}
}
```
**Gemini CLI** (`~/.gemini/settings.json`):
```json
{
"mcpServers": {
"fathom": {
"command": "npx",
"args": ["-y", "fathombridge"],
"env": {
"FATHOM_API_KEY": "your-api-key-here"
}
}
}
}
```
### Step 3 ā Restart Your AI Tool
Restart Claude Code / Cursor / Windsurf and verify:
```
/mcp
```
You should see `fathom` listed as connected.
---
## š ļø Available Tools
| Tool | Description |
| ------------------ | ------------------------------------ |
| `list_meetings` | List meetings with date/team filters |
| `get_transcript` | Full transcript with speaker labels |
| `get_summary` | AI summary + key points |
| `get_action_items` | Action items with owners/due dates |
| `search_meetings` | Search by title, host, participant |
| `list_teams` | List organization teams |
---
## š¬ Example Prompts
Once connected, try these in your AI tool:
```
Show me my last 5 Fathom meetings
Get the transcript from my sprint planning call yesterday
What were the action items from the client call with John?
Search for all meetings about the Q3 roadmap
Show me all meetings from this week with action items
Get the summary of meeting ID abc123
```
---
## š Security
- Your API key is stored only in your local MCP config
- All requests go directly from your machine to Fathom's API
- No data is stored, logged, or transmitted to any third party
- Never commit your API key to version control
---
## š§ Troubleshooting
**`fathom` not showing in `/mcp`**
ā Restart your AI tool after editing the config file
**`Error: FATHOM_API_KEY environment variable is required`**
ā Make sure the env block in your config has your actual API key
**`Error: 401 Unauthorized`**
ā Your API key is invalid ā regenerate it at fathom.video ā Settings ā API
**`No meetings found`**
ā Your API key only accesses meetings recorded by you or shared to your team
**Transcript not available yet**
ā Fathom takes a few minutes to process transcripts after a call ends
---
## š Requirements
- Node.js 18 or higher
- A [Fathom](https://fathom.video) account
- A Fathom API key
---
## š¤ Contributing
Contributions welcome! Please:
1. Fork the repo
2. Create a feature branch
3. Make your changes with tests
4. Submit a PR with a clear description
---
## š License
MIT Ā© 2026 Nauman Pathan
---
## š Acknowledgements
Built on top of the [Model Context Protocol](https://modelcontextprotocol.io)
by Anthropic. Powered by [Fathom](https://fathom.video).
TDQS
Scored across 6 tools
list_meetings and search_meetings both return meetings but are differentiated by filtering/browsing versus searching by text fields. get_summary and get_action_items overlap slightly since summaries include action items, but the dedicated action-item tool has a clear distinct purpose.
All tool names consistently follow a verb_noun snake_case pattern using list, get, or search verbs. There are no mixed conventions or vague generic names.
Six tools is a well-scoped count for a meeting-insights server. Each tool covers a distinct retrieval need without unnecessary bloat or missing core functions.
The server covers core read-only workflows: discovering meetings, searching, retrieving transcripts, summaries, action items, and listing teams. A minor gap is the lack of a dedicated get_meeting endpoint for single-meeting metadata, but list_meetings likely covers that need.