Skip to main content
Glama
WindSeries83

memsem

by WindSeries83
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to memsem

No user-submitted related servers found.

    Related Servers

    • neuromcp

      AdelElo13
      A
      license
      Not graded
      quality
      A
      maintenance
      Semantic memory for AI agents — local-first MCP server with hybrid search, knowledge graph, contradiction detection, and plan-then-commit consolidation.
      286 npm
      4
      AGPL 3.0

    • Memory OS AI

      romainsantoli-web
      A
      license
      Not graded
      quality
      C
      maintenance
      Universal MCP server providing adaptive semantic memory for AI agents, supporting document ingestion, semantic search, chat persistence, cross-project linking, and cloud storage overflow.
      3
      GPL 3.0

    • Selti

      Dek1m
      F
      license
      Not graded
      quality
      B
      maintenance
      A persistent memory server for AI agents using MCP protocol, enabling semantic storage and retrieval of dialogues, documents, and agent states.
      -

    • moss-brain

      Naut1cal5
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides semantic memory with search, related-content traversal, and write-back capabilities, all powered by local embeddings of your notes, documents, and chat histories.
      3
      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.6/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (add vs candidate_add vs episode_add, search vs list vs themes), and descriptions clarify boundaries. However, pairings like memory_add/memory_add_many and memory_forget/memory_purge could cause initial confusion, though the descriptions resolve it.

    Naming Consistency3/5

    All tools share the memory_ prefix, but the suffix pattern is mixed: verbs (add, search, list, verify, score, forget, purge) coexist with nouns (themes, stats, audit, index) and compound actions (candidate_add, episode_search). This inconsistency reduces predictability.

    Tool Count4/5

    At 18 tools, the server is slightly above the ideal 3-15 range but each tool addresses a specific aspect of memory management, from candidate review to episode tracking to scoring. The count feels justified by the domain's complexity rather than redundant.

    Completeness5/5

    The tool set covers the full memory lifecycle: write (add, add_many), review (candidate_*), retrieval (search, list, episode_search), maintenance (verify, score, unsuppress), and deletion (forget, purge), plus auxiliary views (themes, stats, audit, index). No obvious gaps for a semantic memory system.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources