Skip to main content
Glama
nullptr-z

Personal Context Manager

by nullptr-z
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Personal Context Manager

No user-submitted related servers found.

    Related Servers

    • agent-mem0

      ccperdst-lab
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent cross-session memory for Claude Code, enabling it to remember user preferences, decisions, and project context across new sessions.
      Apache 2.0

    • amem

      amanasmuei
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent memory for AI coding tools, allowing them to remember corrections, decisions, and preferences across sessions and different tools.
      19 npm
      2
      MIT
    • pūrmemo by purmemo-ai

      pūrmemoofficial

      purmemo-ai
      A
      license
      A
      quality
      A
      maintenance
      Provides persistent memory for AI assistants like Claude, enabling them to remember user identity, projects, and conversations across sessions and platforms via natural language commands.
      29
      467 npm
      2
      MIT

    • evermemos-mcp-server

      wyh0626
      A
      license
      A
      quality
      D
      maintenance
      Enables AI coding assistants to store and retrieve persistent long-term memory across sessions, remembering project preferences, build steps, and architecture decisions.
      4
      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.8/5.0

    Scored across 8 tools

    Disambiguation3/5

    While most tools target distinct resources (personal context vs. workflow), there is potential overlap between update_context/get_context (personal memory) and workflow_log/workflow_list (project memory) when users mention work-related conventions. The descriptions provide some guidance with specific triggers, but an agent could still confuse which memory store to use for a given piece of information.

    Naming Consistency3/5

    Two different naming patterns are used: context_* tools use verb_noun (update_context, get_context, list_contexts, delete_context) while workflow_* tools use noun_verb (workflow_log, workflow_list, workflow_done). Additionally, generate_prompt follows a third pattern, creating inconsistency across the server's tools.

    Tool Count5/5

    8 tools is a well-scoped count for a personal context manager, covering core operations for two memory systems (personal and project) plus a prompt generator. Each tool appears to earn its place without redundancy.

    Completeness4/5

    The surface offers CRUD operations for personal context (create, read, list, delete) and workflow entries (create, read, update status), covering essential memory management. Minor gaps include the absence of an update tool for personal context (though upsert via update_context covers modification) and no bulk operations or search for workflow entries beyond filtering.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources