Skip to main content
Glama
naumanpathan

FathomBridge

by naumanpathan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to FathomBridge

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 Server

      lukas-bekr
      A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      10
      11 npm
      1
      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 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
      55 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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    list_meetings and search_meetings both return meetings but are differentiated by filtering/browsing versus searching by text fields. get_summary and get_action_items overlap slightly since summaries include action items, but the dedicated action-item tool has a clear distinct purpose.

    Naming Consistency5/5

    All tool names consistently follow a verb_noun snake_case pattern using list, get, or search verbs. There are no mixed conventions or vague generic names.

    Tool Count5/5

    Six tools is a well-scoped count for a meeting-insights server. Each tool covers a distinct retrieval need without unnecessary bloat or missing core functions.

    Completeness4/5

    The server covers core read-only workflows: discovering meetings, searching, retrieving transcripts, summaries, action items, and listing teams. A minor gap is the lack of a dedicated get_meeting endpoint for single-meeting metadata, but list_meetings likely covers that need.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources