Skip to main content
Glama
coolsheng

meeting-memory-mcp

by coolsheng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to meeting-memory-mcp

No user-submitted related servers found.

    Related Servers

    • kb

      okash1n
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that provides a shared context and learning foundation across multiple AI tools (Claude, Copilot, Codex) for multiple projects, enabling persistent knowledge, decisions, and gap reflection through note storage.
      MIT

    • graphify

      Ibrohim-Bxone
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code that stores decisions and summaries locally, enabling Claude to recall past context across chats.
      1
      MIT

    • Claude Conversation Memory

      adamkwhite
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that provides searchable local storage for Claude conversation history, featuring automatic topic extraction and weekly insight summaries. It enables Claude to retrieve context from past sessions through full-text search and organized file storage.
      10
      3
      MIT

    • Cortex

      ProductionLineHQ
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.
      280 npm
      1
      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 7 tools

    Disambiguation5/5

    Tools clearly separate meeting operations (add_meeting, get_meeting, list_meetings, search_meetings) from wiki operations (write_wiki_page, read_wiki_page, list_wiki_pages). Within each domain, each tool serves a distinct purpose with no overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (add_meeting, get_meeting, list_meetings, search_meetings, write_wiki_page, read_wiki_page, list_wiki_pages). No deviations or mixing of conventions.

    Tool Count5/5

    7 tools is a well-scoped set covering two domains (meetings and wiki). Each tool provides essential functionality without unnecessary redundancy, fitting the server's purpose of storing and retrieving meeting transcripts and wiki summaries.

    Completeness4/5

    The tool surface covers core CRUD operations for meetings (add, get, list, search) and wiki (write, read, list). Missing delete and update for meetings, and delete for wiki, but these are minor gaps; agents can work around by writing new wiki pages or relying on search.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources