Skip to main content
Glama
mixelpixx

meMCP - Memory-Enhanced Model Context Protocol

by mixelpixx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to meMCP - Memory-Enhanced Model Context Protocol

No user-submitted related servers found.

    Related Servers

    • MCP Memory Server

      StevenWangler
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides knowledge graph-based persistent memory for LLMs, allowing them to store, retrieve, and reason about information across multiple conversations and sessions.
      9
      114,646 npm
      2
      MIT

    • MCP Memory LibSQL Go

      ZanzyTHEbar
      A
      license
      Not graded
      quality
      C
      maintenance
      🧠 High-performance persistent memory system for Model Context Protocol (MCP) powered by libSQL. Features vector search, semantic knowledge storage, and efficient relationship management - perfect for AI agents and knowledge graph applications.
      7
      MIT

    • FastAPI MCP Server

      purity3
      A
      license
      Not graded
      quality
      D
      maintenance
      A high-performance Model Context Protocol (MCP) server designed for large language models, enabling real-time communication between AI models and applications with support for session management and intelligent tool registration.
      2
      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.8/5.0

    Scored across 24 tools

    Disambiguation3/5

    The tools are organized into clear configuration and memory domains, but there is some ambiguity within each group. For example, config_export and config_validate have unclear boundaries, and memory_stream_* tools could be confused for overlapping streaming operations. Descriptions are missing, making it harder to differentiate, but the prefix structure helps.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with clear prefixes (config_* and memory_*). The naming is highly predictable and organized, making it easy to understand the tool's domain and purpose at a glance.

    Tool Count2/5

    With 24 tools, the count feels excessive for a memory-enhanced protocol. Many tools seem redundant or overly granular (e.g., multiple memory_stream_* actions), suggesting the set could be consolidated without losing functionality. This heavy tool count may overwhelm agents.

    Completeness4/5

    The tool set appears to cover core memory and configuration operations comprehensively, including CRUD-like actions (store, delete, update, query) and management functions (backup, restore, optimize). Minor gaps might exist in advanced querying or integration features, but the surface seems well-rounded for the inferred domain.

    Resources