Fathom AI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FATHOM_API_KEY | Yes | Your Fathom API key |
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 |
|---|---|
| list_meetingsA | List meetings with optional filtering and pagination. All timestamps are UTC. Use get_summary or get_transcript for detailed content. |
| get_transcriptA | Get the transcript for a meeting recording. Returns plaintext lines. For long meetings, use start_time/end_time to fetch a specific window. First call without time params to get metadata (duration, line count), then request specific chunks as needed. |
| get_summaryB | Get summaries for one or more meeting recordings. Returns clean markdown with playback URLs stripped. |
| list_teamsC | List all teams. |
| list_team_membersC | List team members, optionally filtered by team name. |
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 5 tools
Each tool targets a distinct resource or action: summaries, transcripts, meetings list, team members, teams. No overlap in purpose.
All tools follow a consistent verb_noun pattern (get_*, list_*), making the set predictable and easy to navigate.
With 5 tools, the surface is well-scoped for a meeting information retrieval server, covering the core read operations without excess.
The tools cover listing and retrieving meeting details, transcripts, and team info. Minor gaps like search or filtering capabilities might exist but do not hinder basic workflows.