Skip to main content
Glama
catfish-1234

sessionmem

by catfish-1234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to sessionmem

No user-submitted related servers found.

    Related Servers

    • Memex

      arnavbee
      A
      license
      A
      quality
      B
      maintenance
      A local-first, privacy-first MCP server that passively indexes personal digital activity (screenshots, clipboard, notes, downloads, links) into a local database, enabling LLMs like Claude to access your context without cloud storage.
      4
      1
      MIT

    • contextforge-mcp

      alfredoizdev
      A
      license
      A
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based, Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based organization, and team collaboration via Model Context Protocol.
      11
      88 npm
      2
      MIT

    • knitbrain

      PDgit12
      A
      license
      A
      quality
      C
      maintenance
      Local-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.
      37
      10 npm
      6
      MIT

    • codemem

      kunickiaj
      A
      license
      B
      quality
      A
      maintenance
      Persistent memory MCP server that captures coding session context and automatically injects relevant memories into prompts using hybrid search for OpenCode and Claude Code.
      14
      73
      MIT

    • project-memory-mcp

      kaaustubh
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.
      16
      50 npm
      1
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct operations (store, get, forget, list, ingest), and the WHEN TO CALL/NOT sections do a good job of steering selection. However, retrieveMemories, fetch_memories, and startup_inject_memories all overlap as context-retrieval paths, distinguished only by host capability, which invites misselection.

    Naming Consistency3/5

    The majority follow a camelCase verb_noun pattern (storeMemory, retrieveMemories, listMemories, ingestSessionEvents), but startup_inject_memories and fetch_memories break into snake_case, and bare 'stats' deviates. Readable but visibly mixed conventions.

    Tool Count4/5

    13 tools is well within a reasonable range for a memory server with session lifecycle, retrieval, storage, and admin concerns. A couple of the fallback tools are arguably redundant with primary retrieval, but nothing feels padded.

    Completeness3/5

    Create (storeMemory/batchStoreMemory), read (getMemory/retrieveMemories/listMemories), and delete (forgetMemory) are covered, plus session lifecycle and analytics. The notable gap is the absence of a general update/edit operation for an existing memory's content or importance, forcing delete-and-recreate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources