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
      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
      231 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
      26 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
      71
      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
      37 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.3/5.0

    Scored across 13 tools

    Disambiguation3/5

    retrieveMemories, fetch_memories, and startup_inject_memories all perform relevance-based context loading with only host-capability differences, which can cause misselection. summarizeSessionToMemory also overlaps somewhat with handleSessionEnd, though the core CRUD tools are otherwise clearly distinct.

    Naming Consistency3/5

    Most core tools follow a consistent verb_noun camelCase pattern like retrieveMemories, storeMemory, and forgetMemory. However, fetch_memories and startup_inject_memories switch to snake_case, and stats is a bare noun, making the overall convention mixed but still readable.

    Tool Count4/5

    13 tools is a reasonable size for a memory-management server covering basic CRUD, batch operations, statistics, and session-end processing. The count is slightly higher than necessary due to fallback retrieval/injection tools that duplicate or approximate existing functionality.

    Completeness4/5

    The core memory lifecycle is well covered: create, retrieve, search, list, get, delete, batch store, stats, and session summarization. Minor gaps remain, such as no general updateMemory tool and a reference to importMemories that is not actually present in the tool set, but these are workable via delete-and-recreate or existing batch storage.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources