Skip to main content
Glama

Related Servers

Alternatives to SeaMeet MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      The Laxis MCP Server connects Laxis - the AI meeting note taker and voice dictation tool for professionals to Claude and other AI tools through the Model Context Protocol. Your assistant can search and read your meeting transcripts, summaries, and participants directly in chat, turning every conversation you've recorded into context your AI can reason over.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Extended Memory MCP is a Model Context Protocol (MCP) tool that provides cross-session memory storage for Claude Desktop app.
      18
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to join and interact with online meetings (Zoom and Google Meet), capturing transcripts and recordings to generate meeting summaries.
      3
      10
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access Plaud Note recordings, providing direct access to speaker-diarized transcripts and AI-generated meeting summaries. Users can search, list, and retrieve recording details directly within MCP-compatible clients like Claude and Cursor.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Open-source meeting bot API with MCP server. Search, retrieve, and analyze meeting transcripts from Google Meet, Zoom, and Microsoft Teams directly from your AI tools.
      4 npm
      2,811
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose (webhook CRUD, recording retrieval, media URL, usage, status, logout), with no overlapping functionality. Descriptions further clarify boundaries.

    Naming Consistency5/5

    All tools follow the 'seameet_verb_noun' pattern (e.g., seameet_create_webhook, seameet_get_recording), with only minor deviations (seameet_logout, seameet_status) that are still intuitive and consistent with the prefix.

    Tool Count5/5

    10 tools cover webhook management, recording access, usage, and session controls—well-scoped for a meeting recording MCP server. Neither too sparse nor overwhelming.

    Completeness4/5

    Covers core workflows: webhook lifecycle, recording retrieval, media URL, usage, and authentication state. Minor gaps (e.g., no recording deletion or search) but overall sufficient for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive