Fathom MCP Server
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 Server get the transcript from yesterday's meeting with the design team"
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
MCP server for Fathom.video — Access your AI meeting transcripts, summaries, and action items directly from Cursor IDE
A Model Context Protocol (MCP) server that integrates Fathom.video with AI coding assistants like Cursor. Query your meeting transcripts, export recordings to markdown, search by participant, and manage webhooks — all through natural language.
Features
📋 List & Search Meetings — Browse recordings with filters for date, team, participants, or external domains
📝 Full Transcripts — Get speaker-labeled, timestamped transcripts formatted as markdown
📊 AI Summaries — Access Fathom's AI-generated meeting summaries
✅ Action Items — Pull action items from specific meetings or across recent calls
📁 Export to Markdown — Save meetings as
MeetingTitle_YYYY-MM-DD.mdfiles👥 Team Management — List teams and team members
🔔 Webhooks — Create and manage webhooks for real-time notifications
Related MCP server: Fathom MCP Server
Quick Start
1. Get Your Fathom API Key
Go to Fathom Settings
Navigate to API Access
Click Generate API Key
2. Install the MCP Server
git clone https://github.com/matthewbergvinson/fathom-mcp.git
cd fathom-mcp
npm install
npm run build3. Configure Cursor
Add to your ~/.cursor/mcp.json:
{
"mcpServers": {
"fathom": {
"command": "node",
"args": ["/path/to/fathom-mcp/dist/index.js"],
"env": {
"FATHOM_API_KEY": "your-api-key-here",
"FATHOM_OUTPUT_DIR": "/path/to/export/transcripts"
}
}
}
}Note: Replace
/path/to/fathom-mcpwith the actual path where you cloned the repo, and add your Fathom API key.
4. Restart Cursor
Restart Cursor to load the MCP server. You can now use natural language to interact with your Fathom data:
"List my last 5 Fathom meetings"
"Get the transcript from my call with John"
"Export yesterday's meetings to markdown"
"Show me action items from this week"
Available Tools
Meeting Operations
Tool | Description |
| List meetings with filters (date, team, external-only) |
| Get full meeting details including transcript, summary, actions |
| Get just the transcript formatted as markdown |
| Search by participant email, company domain, or team |
Export Operations
Tool | Description |
| Export single meeting to |
| Bulk export meetings with optional date filters |
Action Items
Tool | Description |
| Get action items from a specific meeting or recent calls |
Team Management
Tool | Description |
| List all teams in your organization |
| List team members (optionally filtered by team) |
Webhooks
Tool | Description |
| Create webhook for new meeting notifications |
| Delete an existing webhook |
Tool Parameters
Parameter | Type | Description |
| number | Max meetings to return (0 = all) |
| string | ISO 8601 timestamp filter |
| string | ISO 8601 timestamp filter |
| boolean | Only meetings with external participants |
Parameter | Type | Required | Description |
| number | Yes | The meeting's recording ID |
| boolean | No | Include transcript (default: true) |
| boolean | No | Include AI summary (default: true) |
| boolean | No | Include action items (default: true) |
| boolean | No | Include CRM data (default: true) |
Parameter | Type | Description |
| string[] | Filter by participant emails |
| string[] | Filter by company domains (e.g., |
| string[] | Filter by team names |
| string | ISO 8601 timestamp |
| string | ISO 8601 timestamp |
Parameter | Type | Description |
| number | Meeting to export (export_meeting only) |
| string | Only export after this date |
| string | Only export before this date |
| string | Custom output directory |
Parameter | Type | Required | Description |
| string | Yes | Webhook endpoint URL |
| boolean | No | Include transcript in payload |
| boolean | No | Include summary in payload |
| boolean | No | Include action items |
| boolean | No | Include CRM data |
| string[] | No | Recording types that trigger webhook |
Exported Transcript Format
Exported meetings are saved as markdown with:
Metadata table — Date, duration, participants, Fathom links
AI Summary — Fathom's generated summary
Action Items — With assignees and completion status
Full Transcript — Speaker-labeled with timestamps
Example filename: Quarterly_Business_Review_2024-12-01.md
# Quarterly Business Review
## Meeting Details
| Field | Value |
|-------|-------|
| **Date** | Sunday, December 1, 2024 at 10:00 AM |
| **Duration** | 45m 32s |
| **Recorded by** | Jane Smith <jane@company.com> |
## Participants
- **John Doe** <john@client.com> _(external)_
- **Jane Smith** <jane@company.com>
## Summary
> Key discussion points and outcomes...
## Action Items
- [ ] Follow up on proposal _(assigned to Jane)_
- [x] Send meeting notes
## Transcript
**John Doe** _[00:00:15]_
> Thanks for joining today...Rate Limits
The Fathom API allows 60 requests per minute. The MCP server handles this gracefully.
Security
API keys are stored in Cursor's MCP configuration (not in code)
Never commit your
mcp.jsonor API keys to version controlWebhook secrets should be stored securely
Troubleshooting
MCP not loading?
Ensure you've restarted Cursor after editing
mcp.jsonCheck the path to
dist/index.jsis correctVerify your API key is valid
"fetch failed" errors?
Ensure you're using Node.js 18 or higher
Check your network connection
Verify API key permissions in Fathom settings
Development
# Install dependencies
npm install
# Build TypeScript
npm run build
# Watch mode for development
npm run devLicense
MIT License — see LICENSE for details.
Author
Matthew Bergvinson
Vigilante Consulting
Need Custom AI Tools Built Fast?
We build production-ready MCP servers, AI integrations, and automation tools for businesses.
📧 operations@vigilanteconsulting.com
This MCP server is not officially affiliated with Fathom Video, Inc.
Available Tools
11 toolscreate_webhookD
Inputs: destination_url (required), include_transcript, include_summary, include_action_items, +2 more.
delete_webhookD
Inputs: webhook_id (required).
export_all_meetingsD
Inputs: created_after, created_before, output_dir.
export_meetingD
Inputs: recording_id (required), output_dir.
get_action_itemsD
Inputs: recording_id, include_completed, limit.
get_meetingD
Inputs: recording_id (required), include_transcript, include_summary, include_action_items, +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.
search_meetingsD
Inputs: participant_emails, domains, teams, created_after, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Fathom meeting/team domain. There is no overlap between tools like get_meeting, list_meetings, search_meetings, export_meeting, and export_all_meetings, as they serve different functions (retrieval, listing, searching, exporting).
All tool names follow a consistent verb_noun pattern with snake_case throughout, such as create_webhook, delete_webhook, list_meetings, and get_transcript. This predictability makes it easy for agents to understand and use the toolset without confusion.
With 11 tools, the server is well-scoped for managing meetings, transcripts, action items, teams, and webhooks in the Fathom domain. Each tool earns its place by covering essential operations without being overly sparse or bloated.
The toolset provides comprehensive coverage for core meeting and team management workflows, including CRUD-like operations (e.g., get, list, search, export, create/delete webhooks). A minor gap might be the lack of update or delete tools for meetings or teams, but agents can likely work around this with the existing tools.
Maintenance
Related MCP Connectors
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Give your AI assistant real meeting context via Fathom so every output grounded in your work
Search and analyze meeting transcripts, summaries, soundbites and analytics from Fireflies.ai
Bring meeting decisions, tasks and user stories into your AI editor (Claude, Cursor, Copilot).
Related MCP Servers
- FlicenseNot 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.-
- 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.101MIT
- AlicenseAqualityDmaintenanceEnables Claude to search and retrieve meeting information from Fathom AI through natural language queries.28MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants access to Fathom meeting recordings, summaries, and transcripts via tools like list_meetings, get_meeting_summary, and get_meeting_transcript.MIT