F
licenseNot graded
qualityC
maintenanceEnables querying meeting transcripts, summaries, and action items from Fathom directly in your MCP-compatible AI assistant, eliminating context switching while coding.
-
Fathom MCP Enhanced
by mamba-mental
Related Servers
Alternatives to Fathom MCP Enhanced
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables querying Fathom video meetings: list, search, get transcripts, summaries, and action items.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access Fathom AI meeting data including transcripts, summaries, teams, and team members. Provides tools to list meetings with filters, retrieve detailed transcripts and summaries, and manage team information.11 npmMIT
- AlicenseAqualityAmaintenanceA Model Context Protocol (MCP) server for accessing Fathom AI API endpoints (meetings, recordings, transcripts, summaries, teams, team members) via GET operations.62MIT
- AlicenseAqualityDmaintenanceEnables LLMs to interact with Fathom.video API for managing meeting recordings, retrieving transcripts and AI-generated summaries, searching meeting content, and accessing analytics and team data.1011 npm1MIT
- AlicenseCqualityDmaintenanceEnables access to Fathom.video meeting data including AI-generated transcripts, summaries, and action items. Supports searching meetings, exporting to markdown, and managing webhooks through natural language in Cursor IDE.1155 npm6MIT
TDQS
C2/5.0
Scored across 14 tools
Disambiguation3/5
Tool names are mostly distinct, but several overlap in purpose: participant_stats vs. meeting_stats, search_meetings vs. search_content, and get_meeting vs. get_transcript vs. export_meeting. Without any descriptions, an agent must guess the exact boundaries, making misselection likely in these clusters.
Naming Consistency5/5
All tool names use consistent snake_case and follow a clear verb_noun or noun_noun pattern: list_meetings, get_meeting, export_meeting, search_meetings, create_webhook, delete_webhook, etc. The two stats tools (participant_stats, meeting_stats) are noun phrases but still fit the predictable naming style.
Tool Count5/5
Fourteen tools is well within the ideal range for a meeting-intelligence server. The set covers core read, search, export, stats, team, and webhook operations without obvious bloat or missing essentials.
Completeness4/5
The surface covers meetings, transcripts, exports, search, stats, action items, teams, and webhooks, which is strong for a read-oriented recording platform. Minor gaps exist in webhook management (no list/get/update) and deeper team or participant detail, but agents can work around them.
Maintenance
ActivityInactive
ResponsivenessNo issues