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 (get it from Fathom Settings > API Access) | |
| FATHOM_OUTPUT_DIR | No | Path to export transcripts (optional, used for export operations) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_meetingsD | – |
| get_meetingD | – |
| get_transcriptD | – |
| export_meetingD | – |
| export_all_meetingsD | – |
| search_meetingsD | – |
| get_action_itemsD | – |
| list_teamsD | – |
| list_team_membersD | – |
| create_webhookD | – |
| delete_webhookD | – |
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 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.