Fathom AI 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 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| list_teamsA | List all teams accessible to the authenticated user. Returns a paginated list of teams with their names and creation dates. |
| list_team_membersA | List team members accessible to the authenticated user. Can be filtered by team name. Returns member names, emails, and creation dates. |
| create_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. |
| delete_webhookA | Delete a webhook by its ID. Returns a success message if the webhook was deleted successfully. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_api_info | Get information about the Fathom API. |
| get_rate_limits | Get information about API rate limits. |
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.