Fathom MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FATHOM_API_KEY | Yes | Your Fathom API key for authentication. Get it from Settings > API in your Fathom account at https://fathom.video |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fathom_list_meetingsA | List meetings from Fathom with optional filtering and pagination. This tool retrieves meeting recordings from your Fathom account. You can filter by:
You can optionally include:
Args:
Returns: Paginated list of meetings with requested details. Examples:
|
| fathom_get_summaryA | Get the AI-generated summary for a specific Fathom recording. This tool retrieves the summary that Fathom automatically generates for each meeting. The summary includes key discussion points, decisions made, and important topics covered. Args:
Returns: The meeting summary with template name and formatted content. Examples:
Notes:
|
| fathom_get_transcriptA | Get the full transcript for a specific Fathom recording. This tool retrieves the complete timestamped transcript of a meeting, including speaker identification and timestamps for each segment. Args:
Returns: Array of transcript entries, each containing:
Examples:
Notes:
|
| fathom_list_teamsA | List all teams accessible to the authenticated user in Fathom. This tool retrieves the list of teams in your Fathom workspace. Teams are used to organize recordings and control access to meeting content. Args:
Returns: Paginated list of teams with:
Examples:
|
| fathom_list_team_membersA | List members of a specific team or all teams in Fathom. This tool retrieves team member information including names, emails, and when they joined. Args:
Returns: Paginated list of team members with:
Examples:
|
| fathom_create_webhookA | Create a webhook to receive real-time notifications when meetings are processed in Fathom. This tool creates a webhook subscription that will POST meeting data to your specified URL whenever new meeting content becomes available. Args:
Returns: The created webhook details including:
Examples:
Notes:
|
| fathom_delete_webhookA | Delete an existing webhook from Fathom. This tool removes a webhook subscription, stopping all future notifications to that endpoint. Args:
Returns: Confirmation of successful deletion. Examples:
Notes:
|
| fathom_search_meetingsA | Search across Fathom meeting titles, transcripts, and summaries. This tool performs a text search across your meeting content to find relevant discussions, mentions, or topics. Args:
Returns: Matching meetings with:
Examples:
Notes:
|
| fathom_meeting_statsA | Get analytics and statistics about your Fathom meetings. This tool calculates aggregate statistics about your meetings including duration metrics, team breakdowns, and internal vs external meeting ratios. Args:
Returns:
Examples:
Notes:
|
| fathom_participant_statsA | Get analytics about meeting participants and recorders in Fathom. This tool analyzes who attends your meetings most frequently and which domains are most common. Args:
Returns:
Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a distinct purpose with clear boundaries: webhook management (create/delete), meeting data retrieval (list, get summary/transcript, search), team management (list teams/members), and analytics (meeting/participant stats). There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.
All tool names follow a consistent 'fathom_' prefix with snake_case and a clear verb_noun pattern (e.g., fathom_create_webhook, fathom_list_meetings, fathom_get_summary). This uniformity enhances readability and predictability across the toolset.
With 10 tools, the server is well-scoped for managing Fathom meeting data, covering key operations like CRUD for webhooks, retrieval of meeting details, team management, analytics, and search. Each tool serves a unique and necessary function without bloat or gaps.
The toolset provides comprehensive coverage for the Fathom meeting domain, including full lifecycle management (create/delete webhooks), data access (list, get, search), team organization, and analytics. There are no obvious gaps; agents can perform all essential workflows without dead ends.