Skip to main content
Glama
gabrimatic

mcp-prose-memory

by gabrimatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-prose-memory

No user-submitted related servers found.

    Related Servers

    • mnemonic-mcp

      c1hucktay4lors
      A
      license
      A
      quality
      B
      maintenance
      Persistent memory server for MCP clients that lets AI assistants remember facts about users across sessions via a single markdown file, with tools to read, save, search, update, delete, and organize memory.
      10
      MIT

    • mcp-memory-vault

      AleBrito124356
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives agents persistent memory with namespaced facts, tags, full-text search, and TTL expiry, all running locally on SQLite with zero external dependencies.
      8
      3
      MIT
    • adl-context-collector by ammons-datalabs

      adl-context-collectorofficial

      ammons-datalabs
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing persistent memory for LLMs via semantic search over captures, structured facts with temporal tracking, and document ingestion. Enables any MCP-compatible client to maintain a searchable knowledge base across sessions.
      -

    • Agent Memory

      Masikomoore
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.
      3
      -

    • agenticmemory

      jyswee
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory MCP server for AI agents that stores, recalls, and searches conversation history, key-value context, and long-term entries across sessions with semantic search and FIFO queues.
      235 npm
      1
      -
    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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: 'memory' handles CRUD operations on memories, while 'memory_context' loads memory for session start. No overlap or ambiguity.

    Naming Consistency4/5

    Both tool names start with 'memory' and use underscores for compound names, following a consistent pattern. However, 'memory' is a single noun while 'memory_context' is a compound noun, a minor deviation.

    Tool Count3/5

    With only 2 tools, the server is lean. All CRUD operations are bundled into one tool, which works but limits granularity. The count is on the low side but acceptable given the internal richness.

    Completeness4/5

    The 'memory' tool covers all standard CRUD operations (view, add, upsert, remove, replace), and 'memory_context' handles context loading. Minor gaps like listing sections or clearing all memories are missing but not critical.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources