Fathom MCP Enhanced
Provides tools for interacting with Fathom.video, including listing meetings, retrieving transcripts, managing teams, webhooks, and analytics.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fathom MCP Enhanced show me my action items from this week's meetings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fathom MCP Enhanced
An enhanced MCP (Model Context Protocol) server for Fathom.video that provides comprehensive access to AI meeting transcripts, summaries, action items, team management, webhooks, and powerful analytics.
This project combines the best features from multiple Fathom MCP implementations:
Core functionality from matthewbergvinson/fathom-mcp
Analytics tools ported from lukas-bekr/fathom-mcp
Features
14 Tools Available
Core Meeting Tools
Tool | Description |
| List meetings with filters (date range, external participants only) |
| Get full meeting details including transcript, summary, action items, CRM matches |
| Get just the transcript for a specific meeting |
| Export a single meeting to a formatted markdown file |
| Batch export all meetings to markdown files |
| Search meetings by participant email, company domain, or team |
| Get action items from one or multiple recent meetings |
Team Management
Tool | Description |
| List all teams in your Fathom organization |
| List members of a specific team or all teams |
Webhooks
Tool | Description |
| Create a webhook for meeting notifications |
| Delete an existing webhook |
Analytics (Enhanced)
Tool | Description |
| Full-text search across meeting transcripts and summaries with context snippets |
| Get comprehensive meeting statistics (duration averages, internal/external ratio, team breakdown) |
| Analyze participant frequency, top recorders, and domain distribution |
Related MCP server: Fathom-Simple-MCP
Installation
Prerequisites
Node.js 18.0.0 or higher
A Fathom.video account with API access
Your Fathom API key
Setup
# Clone the repository
git clone https://github.com/mamba-mental/fathom-mcp-enhanced.git
cd fathom-mcp-enhanced
# Install dependencies
npm install
# Build the TypeScript
npm run buildConfiguration
Environment Variables
Variable | Required | Description |
| Yes | Your Fathom API key |
| No | Custom directory for exported transcripts (defaults to |
Getting Your Fathom API Key
Log into Fathom.video
Go to Settings → Integrations → API
Generate a new API key
Copy the key for use in configuration
Claude Desktop Integration
Add the following to your claude_desktop_config.json:
Windows
{
"mcpServers": {
"fathom": {
"command": "node",
"args": ["C:/mcp/fathom-mcp-enhanced/dist/index.js"],
"env": {
"FATHOM_API_KEY": "your_fathom_api_key_here",
"FATHOM_OUTPUT_DIR": "C:/Users/YourName/Documents/FathomTranscripts"
}
}
}
}macOS/Linux
{
"mcpServers": {
"fathom": {
"command": "node",
"args": ["/path/to/fathom-mcp-enhanced/dist/index.js"],
"env": {
"FATHOM_API_KEY": "your_fathom_api_key_here",
"FATHOM_OUTPUT_DIR": "/home/user/FathomTranscripts"
}
}
}
}Usage Examples
List Recent Meetings
Show me my last 10 meetings using list_meetingsSearch Meeting Content
Use search_content to find all meetings where we discussed "quarterly budget"Get Meeting Analytics
Use meeting_stats to analyze all my meetings from the last 30 daysAnalyze Participants
Use participant_stats to show me who I meet with most frequentlyCredits
This enhanced version combines work from multiple sources:
Original Core Implementation: matthewbergvinson/fathom-mcp by Matthew Bergvinson
Analytics Tools: Ported from lukas-bekr/fathom-mcp by Lukas Bekr
Enhanced & Combined: Big Brother Master Journey (Prime)
License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
14 toolscreate_webhookD
Inputs: destination_url (required), triggered_for, include_summary, include_transcript, +2 more.
delete_webhookD
Inputs: webhook_id (required).
export_all_meetingsD
Inputs: output_dir, created_after, created_before.
export_meetingD
Inputs: recording_id (required), output_dir.
get_action_itemsD
Inputs: limit, recording_id, include_completed.
get_meetingD
Inputs: recording_id (required), include_summary, include_transcript, include_crm_matches, +1 more.
get_transcriptD
Inputs: recording_id (required).
list_meetingsD
Inputs: limit, created_after, created_before, include_external_only.
list_team_membersD
Inputs: team.
list_teamsD
Inputs: no named parameters.
meeting_statsD
Inputs: teams, created_after, created_before.
participant_statsD
Inputs: limit, created_after, created_before.
search_contentD
Inputs: query (required), limit, teams, created_after, +1 more.
search_meetingsD
Inputs: teams, domains, created_after, created_before, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Tool names are mostly distinct, but several overlap in purpose: participant_stats vs. meeting_stats, search_meetings vs. search_content, and get_meeting vs. get_transcript vs. export_meeting. Without any descriptions, an agent must guess the exact boundaries, making misselection likely in these clusters.
All tool names use consistent snake_case and follow a clear verb_noun or noun_noun pattern: list_meetings, get_meeting, export_meeting, search_meetings, create_webhook, delete_webhook, etc. The two stats tools (participant_stats, meeting_stats) are noun phrases but still fit the predictable naming style.
Fourteen tools is well within the ideal range for a meeting-intelligence server. The set covers core read, search, export, stats, team, and webhook operations without obvious bloat or missing essentials.
The surface covers meetings, transcripts, exports, search, stats, action items, teams, and webhooks, which is strong for a read-oriented recording platform. Minor gaps exist in webhook management (no list/get/update) and deeper team or participant detail, but agents can work around them.
Related MCP Connectors
Fathom MCP server for ChatGPT, Claude and any AI agent: list calls, complete action item, add action item, share call, set link access, regenerate summary, update settings and delete call in your own Fathom account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Fathom yourself; Cotlet does not store your password and you need no Fathom API key. About the official Fathom API: Fathom has a REST API and an official MCP server, but both only read your calls (checked 22 Oct 2026). The API lists meetings and returns summaries, transcripts and action items, requests recording downloads and manages webhooks. Setup and FAQ: https://cotlet.dev/integrations/fathom-video-api-mcp-server
Search, read, analyze and create HappyScribe transcripts and meeting notes from any MCP client
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Official Akiflow MCP for tasks, calendars, scheduling, time slots, and meeting transcripts.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access Fathom AI meeting data including transcripts, summaries, teams, and team members. Provides tools to list meetings with filters, retrieve detailed transcripts and summaries, and manage team information.16 npmMIT
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server for accessing Fathom AI API endpoints (meetings, recordings, transcripts, summaries, teams, team members) via GET operations.62MIT
- AlicenseCqualityDmaintenanceEnables access to Fathom.video meeting data including AI-generated transcripts, summaries, and action items. Supports searching meetings, exporting to markdown, and managing webhooks through natural language in Cursor IDE.1120 npm6MIT
- AlicenseAqualityDmaintenanceEnables LLMs to interact with Fathom.video API for managing meeting recordings, retrieving transcripts and AI-generated summaries, searching meeting content, and accessing analytics and team data.1016 npm1MIT