A
licenseA
qualityA
maintenanceA Model Context Protocol (MCP) server for accessing Fathom AI API endpoints (meetings, recordings, transcripts, summaries, teams, team members) via GET operations.
6
2
MIT
fathom-mcp-adapter
Related Servers
Alternatives to fathom-mcp-adapter
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server for the Fathom AI meeting intelligence API555 npmMIT
- FlicenseAqualityDmaintenanceRead-only MCP server that exposes Grafana dashboards, datasources, and metric/log queries as tools, for use by skills in the TICKETS workspace.6-
- AlicenseCqualityDmaintenanceProvides comprehensive MCP tools for Fathom.video meetings, including transcripts, summaries, action items, team management, webhooks, and analytics.14MIT
- AlicenseAqualityBmaintenanceEnables Claude Desktop and MCP clients to access Fathom meeting intelligence, including listing meetings, retrieving summaries and transcripts, and searching by title.434 npmMIT
- FlicenseNot gradedqualityBmaintenanceHosted MCP server that lets staff search and retrieve AskElephant call transcripts from claude.ai, with tools for listing meetings, searching transcript excerpts, and fetching full transcripts.-
TDQS
A4/5.0
Scored across 4 tools
Disambiguation4/5
The tools are mostly distinct: health, list, get_latest, and transcript each serve a clear purpose. Slight overlap exists between list_recent_meetings and get_latest_meeting, but the distinction (multiple vs. single) is clear from descriptions.
Naming Consistency4/5
All tools share the 'fathom_' prefix and most follow a verb_noun pattern (list_, get_). However, 'fathom_health' lacks an explicit verb, deviating slightly from the otherwise consistent convention.
Tool Count5/5
With 4 tools, the server is well-scoped for a focused read-only meeting adapter. Each tool covers a necessary operation without redundancy or bloat.
Completeness4/5
The surface covers health, listing, latest meeting, and transcript retrieval, which are the core read operations. A minor gap is the lack of a direct 'get meeting by recording_id' endpoint, though it can be worked around via list filtering.
Maintenance
ActivityInactive
ResponsivenessNo issues