Skip to main content
Glama
lukas-bekr

Fathom MCP Server

by lukas-bekr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Fathom MCP Server

No user-submitted related servers found.

    Related Servers

    • Fathom MCP Server

      bondjacobbond
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      10 npm
      MIT

    • Fathom MCP Server

      stussy446
      F
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to the Fathom meeting recording API to retrieve meeting summaries, transcripts, and action items.
      -

    • Fathom MCP Server

      matthewbergvinson
      A
      license
      C
      quality
      D
      maintenance
      Enables 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.
      11
      5 npm
      6
      MIT

    • fathom-mcp

      jhamman
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants access to Fathom meeting recordings, summaries, and transcripts via tools like list_meetings, get_meeting_summary, and get_meeting_transcript.
      MIT

    • Fathom Video MCP Server

      trevorwelch
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Fathom meeting recordings, enabling users to list meetings with filters, retrieve AI-generated summaries, and access full transcripts with speaker attribution and timestamps.
      3
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose with clear boundaries: webhook management (create/delete), meeting data retrieval (list, get summary/transcript, search), team management (list teams/members), and analytics (meeting/participant stats). There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.

    Naming Consistency5/5

    All tool names follow a consistent 'fathom_' prefix with snake_case and a clear verb_noun pattern (e.g., fathom_create_webhook, fathom_list_meetings, fathom_get_summary). This uniformity enhances readability and predictability across the toolset.

    Tool Count5/5

    With 10 tools, the server is well-scoped for managing Fathom meeting data, covering key operations like CRUD for webhooks, retrieval of meeting details, team management, analytics, and search. Each tool serves a unique and necessary function without bloat or gaps.

    Completeness5/5

    The toolset provides comprehensive coverage for the Fathom meeting domain, including full lifecycle management (create/delete webhooks), data access (list, get, search), team organization, and analytics. There are no obvious gaps; agents can perform all essential workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources