Skip to main content
Glama
Dot-Fun

Fathom AI MCP Server

by Dot-Fun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Fathom AI MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

      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 AI MCP Server

      apspan
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes the Fathom AI meeting intelligence API to Claude, allowing users to list meetings, fetch transcripts, and retrieve summaries. It also enables management of teams and members through the Model Context Protocol.
      45 npm
      MIT

    • 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
      54 npm
      6
      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.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: meetings, summaries, transcripts, teams, team members, and webhooks. Even though get_summary and get_transcript both retrieve meeting content, their purposes are clearly different and list_meetings can include optional content without overlapping directly.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern with lowercase and underscores, such as list_meetings, get_summary, and create_webhook. There are no mixed conventions or vague verbs, making the API predictable.

    Tool Count5/5

    The 7 tools are well-scoped for a meeting AI assistant covering the core actions of browsing meetings, retrieving content, listing teams, and managing webhooks. The count is neither too sparse nor excessive.

    Completeness4/5

    The core workflow of listing meetings and retrieving summaries/transcripts is well-covered, along with team management and webhook lifecycle. Minor gaps exist, such as no explicit list_webhooks or update_meeting, but these are not critical for the primary use case.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources