Skip to main content
Glama
mikhashev

Personal Context Technology MCP Server

by mikhashev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Personal Context Technology MCP Server

No user-submitted related servers found.

    Related Servers

    • Personal Context Manager

      nullptr-z
      F
      license
      A
      quality
      D
      maintenance
      Provides persistent personal context storage across AI conversations, allowing AI assistants to remember user preferences, project conventions, and other personal information between sessions.
      8
      -

    • recall

      andrewhomeyer
      A
      license
      A
      quality
      D
      maintenance
      Gives AI assistants a persistent memory across conversations, allowing them to remember user preferences, notes, and facts between chats.
      6
      54 npm
      MIT

    • octobrain

      Muvon
      A
      license
      Not graded
      quality
      A
      maintenance
      Persistent memory for AI assistants — store insights, decisions, and knowledge that survives across conversations.
      14
      Apache 2.0

    • Mnemosyne

      kharshita590
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent memory for LLM applications, enabling AI assistants to remember user preferences, facts, and conversation history across sessions.
      1
      -

    • Recall

      joseairosa
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, cross-session memory for AI agents, allowing them to store and automatically retrieve information across different conversations and sessions without repeating context.
      3 npm
      174
      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

    D1.2/5.0

    Scored across 1 tool

    Disambiguation1/5

    Only one tool exists, so there is no ambiguity among tools. However, the lack of description means it's impossible to understand its purpose, making selection meaningless.

    Naming Consistency3/5

    The single tool uses camelCase. With only one tool, consistency cannot be evaluated meaningfully, so a neutral score is given.

    Tool Count1/5

    A single tool with no description is far too few for a meaningful server. It suggests minimal utility and incomplete implementation.

    Completeness1/5

    With only one tool and no description, the tool surface is severely incomplete. The server's purpose is unknown, and no workflows can be supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources