Skip to main content
Glama

Related Servers

Alternatives to cogsession

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that captures and recalls coding session memory (failures, decisions, diffs) for AI agents, enabling cross-agent continuity and preventing repeated mistakes.
      78 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Persistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.
      1
      MIT
    • A
      license
      A
      quality
      C
      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
      67 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server gives Claude Code persistent cross-session memory with semantic search, automatic detection and tracking of user corrections as behavioral patterns, and reflective framework evolution that improves judgment over time. Everything runs locally through Claude Code's hooks and extension points, with no cloud, accounts, or API keys required.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory MCP server for Claude Code that stores decisions and summaries locally, enabling Claude to recall past context across chats.
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct — checkpoint/update, tree/search/log/status, and claim_record/claim_check each serve different purposes. The main ambiguity is session_init and session_load, since both are meant to be called at session start and both reference continuation from previous sessions, though their outputs differ.

    Naming Consistency4/5

    The session_ prefix gives the set a strong, consistent identity, and all names use lowercase_with_underscores. However, operations mix imperative verbs (init, load, update) with noun-style view commands (tree, status, log, diagram), and the claim_* pair breaks the session_ prefix pattern.

    Tool Count5/5

    11 tools is well-scoped for a session-management server. Each tool covers a distinct part of the workflow — lifecycle, history, search, status, claims, and diagram — and none feels redundant or unnecessary.

    Completeness4/5

    The core lifecycle is well covered: init, update, checkpoint, load, plus history, search, status, claims, and diagram. Minor gaps exist — there is no explicit session_end/archive tool and no way to delete or supersede a claim — but agents can complete the main workflow without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues