Fathom AI MCP Server
Provides tools for managing and accessing meeting recordings, summaries, transcripts, teams, and webhooks through the Fathom AI API.
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 AI MCP Server show me meetings from last week with transcripts and summaries"
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 AI MCP Server
A Model Context Protocol (MCP) server for interacting with the Fathom AI API. This server provides tools for accessing meeting recordings, summaries, transcripts, teams, and webhooks.
Quick Start
git clone https://github.com/Dot-Fun/fathom-mcp.git
cd fathom-mcp
uv pip install fastmcp httpx pydantic
export FATHOM_API_KEY="your_api_key_here"
fastmcp run server.pyRelated MCP server: Fathom AI MCP Server
Features
Tools
list_meetings: List meetings with advanced filtering (by participants, date ranges, teams) and optional inclusion of transcripts, summaries, action items, and CRM matches
get_summary: Retrieve meeting summaries (supports async delivery)
get_transcript: Retrieve meeting transcripts with speaker information and timestamps (supports async delivery)
list_teams: List all accessible teams
list_team_members: List team members with optional team filtering
create_webhook: Create webhooks for meeting notifications with customizable triggers and content inclusion
delete_webhook: Delete webhooks by ID
Resources
fathom://api/info: API information and available endpoints
fathom://api/rate-limits: Rate limiting information and best practices
Installation
Clone this repository or copy the files to your local machine
Install dependencies using uv (recommended) or pip:
# Using uv (recommended)
uv pip install -e .
# Or using pip
pip install -e .Set up your Fathom API key:
Create a .env file in the project root:
FATHOM_API_KEY=your_api_key_hereThe server auto-loads .env for local usage.
Get your API key from the Fathom settings page.
Usage
Running the Server
Local Development (stdio)
# Using fastmcp CLI
fastmcp run server.py
# Or directly with Python
python server.pyHTTP Server
# Modify server.py to run as HTTP server
if __name__ == "__main__":
mcp.run(transport="http", host="0.0.0.0", port=8000)Integrating with Claude Desktop
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"fathom": {
"command": "uv",
"args": [
"--directory",
"/path/to/fathom-mcp",
"run",
"fastmcp",
"run",
"server.py"
],
"env": {
"FATHOM_API_KEY": "your_api_key_here"
}
}
}
}Integrating with Codex (alternative)
Add this block to your Codex config (~/.codex/config.toml):
[mcp_servers.fathom]
command = "uv"
args = ["--directory", "/path/to/fathom-mcp", "run", "fastmcp", "run", "server.py"]Then restart Codex (or reload MCP servers) and verify:
codex mcp listAPI Reference
Authentication
All requests require the FATHOM_API_KEY environment variable. API keys are user-level and can access:
Meetings recorded by the user
Meetings shared to the user's team
Rate Limits
Global limit: 60 API calls per 60-second window
Rate-limited requests return HTTP 429
Monitor rate limit headers:
RateLimit-Limit,RateLimit-Remaining,RateLimit-Reset
Tool Examples
List Recent Meetings
# List meetings with transcripts from the last week
result = await list_meetings(
created_after="2024-01-01T00:00:00Z",
include_transcript=True,
include_summary=True
)Get Meeting Summary
# Get summary for a specific recording
summary = await get_summary(recording_id=123456789)Create a Webhook
# Create webhook for team recordings with all content
webhook = await create_webhook(
destination_url="https://your-app.com/webhook",
triggered_for=["my_recordings", "shared_team_recordings"],
include_transcript=True,
include_summary=True,
include_action_items=True,
include_crm_matches=True
)
# Returns webhook ID, URL, and secret for signature verificationFilter Meetings by Participants
# Find meetings with specific participants
meetings = await list_meetings(
calendar_invitees=["alice@acme.com", "bob@acme.com"],
include_action_items=True
)List Team Members
# Get all members of the Sales team
members = await list_team_members(team="Sales")Error Handling
The server handles common API errors:
401 Unauthorized: Invalid or missing API key
400 Bad Request: Invalid parameters
404 Not Found: Resource doesn't exist
429 Rate Limited: Too many requests (includes reset time)
Development
Project Structure
fathom-mcp/
├── server.py # Main MCP server implementation
├── pyproject.toml # Project configuration and dependencies
├── Dockerfile # Container configuration for deployment
├── package.json # Package metadata
├── README.md # This file
├── .env # Environment variables (API key)
└── .dockerignore # Docker build exclusionsCode Quality
The project uses Ruff for linting and formatting:
# Install dev dependencies
uv pip install -e ".[dev]"
# Run linter
ruff check .
# Auto-fix issues
ruff check --fix .
# Format code
ruff format .Testing
The server has been tested with real Fathom API data. See TEST_RESULTS.md for detailed test results.
To test manually:
# Set your API key
export FATHOM_API_KEY="your_api_key_here"
# Test server loads
python -c "from server import mcp; print('✓ Server ready')"
# Test API connectivity
python -c "
import asyncio
from server import make_request
asyncio.run(make_request('GET', '/meetings'))
"API Documentation
For complete API documentation, visit:
License
This project is open source and available under the MIT License.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Support
Issues: GitHub Issues
Fathom API: Fathom Support
MCP Protocol: MCP Documentation
Acknowledgments
Built with FastMCP - The fast, Pythonic way to build MCP servers.
Repository
Available Tools
7 toolscreate_webhookA
Create a new webhook for receiving meeting notifications.
At least one of the include_* flags must be true. The webhook will be triggered for the specified recording types and will include the requested content.
Returns the webhook ID, URL, secret (for signature verification), and configuration.
Inputs: triggered_for (required), destination_url (required), include_summary, include_transcript, +2 more. Returns: object
delete_webhookA
Delete a webhook by its ID.
Returns a success message if the webhook was deleted successfully.
Inputs: webhook_id (required). Returns: object
get_summaryA
Get the summary for a specific meeting recording.
If destination_url is provided, the summary will be delivered asynchronously to that URL. Otherwise, the summary is returned directly.
Inputs: recording_id (required), destination_url. Returns: object
get_transcriptA
Get the transcript for a specific meeting recording.
If destination_url is provided, the transcript will be delivered asynchronously to that URL. Otherwise, the transcript is returned directly. The transcript includes speaker information, text, and timestamps.
Inputs: recording_id (required), destination_url. Returns: object
list_meetingsA
List meetings recorded by or shared with the authenticated user.
Supports pagination via cursor and various filtering options including participants, date ranges, recording users, and teams. Can optionally include action items, CRM matches, summaries, and transcripts.
Inputs: teams, cursor, recorded_by, created_after, +8 more. Returns: object
list_team_membersA
List team members accessible to the authenticated user.
Can be filtered by team name. Returns member names, emails, and creation dates.
Inputs: team, cursor. Returns: object
list_teamsA
List all teams accessible to the authenticated user.
Returns a paginated list of teams with their names and creation dates.
Inputs: cursor. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: meetings, summaries, transcripts, teams, team members, and webhooks. Even though get_summary and get_transcript both retrieve meeting content, their purposes are clearly different and list_meetings can include optional content without overlapping directly.
All tool names follow the verb_noun pattern with lowercase and underscores, such as list_meetings, get_summary, and create_webhook. There are no mixed conventions or vague verbs, making the API predictable.
The 7 tools are well-scoped for a meeting AI assistant covering the core actions of browsing meetings, retrieving content, listing teams, and managing webhooks. The count is neither too sparse nor excessive.
The core workflow of listing meetings and retrieving summaries/transcripts is well-covered, along with team management and webhook lifecycle. Minor gaps exist, such as no explicit list_webhooks or update_meeting, but these are not critical for the primary use case.
Maintenance
Related MCP Connectors
Give your AI assistant real meeting context via Fathom so every output grounded in your work
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.
Let AI assistants record meetings and work with notes, transcripts, contacts, and Drive.
Related MCP Servers
- 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
- AlicenseNot gradedqualityDmaintenanceExposes the Fathom AI meeting intelligence API to Claude, allowing users to list meetings, fetch transcripts, and retrieve summaries. It also enables management of teams and members through the Model Context Protocol.46 npmMIT
- 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
- AlicenseAqualityDmaintenanceConnects AI tools to Fathom meeting transcripts, summaries, and action items via a single API key.62 npmMIT