MCP Fathom Server
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_meetingsB | List Fathom meetings with optional filters. Returns meeting titles, summaries, dates, and participants. |
| search_meetingsA | Search for meetings containing keywords in titles, summaries, or action items. NOTE: Searches last 30 days only. For better performance, transcript search is disabled by default. |
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 2 tools
list_meetings and search_meetings have clearly distinct purposes: one filters and lists meetings, the other performs keyword search. No ambiguity.
Both tools use consistent verb_noun pattern: list_meetings and search_meetings. Naming is predictable and clear.
With only 2 tools, the server is minimal but appears focused on read operations for meeting data. The count is slightly low but appropriate for its narrow scope.
The set covers listing and searching meetings, which covers common read operations. However, there is no tool to retrieve a specific meeting by ID, a minor gap.