Fathom Video 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 Fathom meetings with optional filtering. Returns a paginated list of meetings. Use the recording_id from the results to fetch summaries or transcripts with get_summary or get_transcript. |
| get_summaryA | Get the AI-generated summary for a specific meeting recording. Returns a markdown-formatted summary of the meeting including key points and discussion topics. |
| get_transcriptA | Get the full transcript for a specific meeting recording. Returns timestamped transcript segments with speaker attribution. Each segment includes the speaker name, what they said, and when. |
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 3 tools
Each tool has a clearly distinct purpose: listing meetings, retrieving summaries, and fetching transcripts. No overlap or ambiguity exists.
All tool names follow a consistent verb_noun pattern using snake_case (list_meetings, get_summary, get_transcript), making them predictable and easy to understand.
With 3 tools, the server is well-scoped for its purpose of accessing meeting recordings. Each tool is necessary and there are no superfluous tools.
The tool set covers the core workflow: listing meetings, then retrieving either the summary or transcript. No obvious gaps exist for the stated domain.