Skip to main content
Glama
Sign In
SeaMeet MCP

SeaMeet MCP

Official
by seameet-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to SeaMeet MCP

No user-submitted related servers found.

    Related Servers

    • Extended Memory MCP

      ssmirnovpro
      A
      license
      Not graded
      quality
      D
      maintenance
      Extended Memory MCP is a Model Context Protocol (MCP) tool that provides cross-session memory storage for Claude Desktop app.
      18
      MIT

    • Finch MCP

      finchagentic
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to retain persistent, searchable memory and versioned vaults, spawn and recall named agents with state and audit history, run automations, monitors, and deep research, and execute on-chain and web tasks across sessions. It can be installed alongside Claude Code, Cursor, Windsurf, Zed, Hermes, and other MCP clients, with vault and memory optionally run entirely on the user's machine.
      45
      235 npm
      MIT
    • LoreConvo

      LoreConvoofficial

      labyrinth-analytics
      A
      license
      A
      quality
      A
      maintenance
      Persistent memory for AI agents across Claude Code, Cowork, Codex, Cursor and Hermes Agent. Saves, searches and recalls sessions from a local SQLite store through 40+ MCP tools, with auto-save and auto-load hooks, project tagging and export/import. Also a Hermes Agent memory provider plugin in the official catalog. Free: keyword search, 50 sessions. Pro ($8/mo): semantic search and team memory.
      33
      102 PyPI
      12
      Business Source 1.1

    • cogmemai-mcp

      hifriendbot
      A
      license
      A
      quality
      C
      maintenance
      Persistent cloud memory for AI coding assistants. 28 MCP tools for semantic search, auto-learning, task tracking, correction patterns, knowledge graphs, and session replay across Claude Code, Cursor, Windsurf, Cline, and any MCP client. Encrypted at rest. Team shared memory with author attribution.
      35
      992 npm
      7
      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 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

    ActivityMaintained
    ResponsivenessLimited data

    Resources