Skip to main content
Glama
AppleLamps

MemoryPatch

by AppleLamps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MemoryPatch

No user-submitted related servers found.

    Related Servers

    • tartarus-mcp

      saluca-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.
      1 npm
      1
      Apache 2.0

    • heropen

      Koradji77
      A
      license
      Not graded
      quality
      A
      maintenance
      A local memory server for AI agents that stores and retrieves information via MCP, keeping all data in SQLite on your machine.
      165 PyPI
      1
      Apache 2.0

    • agent-memory

      khaled1174
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing persistent memory management for AI agents using SQLite and FTS5, enabling storage, full-text search, and recall of memories with namespace isolation.
      1
      MIT

    • server-memory

      MK-986123
      A
      license
      A
      quality
      B
      maintenance
      A local-first MCP server for durable agent memory using SQLite and FTS5, enabling knowledge graph storage, search, and recall for AI agents.
      20
      1
      MIT

    • memdb

      j0hanz
      A
      license
      A
      quality
      D
      maintenance
      A SQLite-backed MCP memory server providing persistent memory storage with full-text search and knowledge graph capabilities for AI assistants.
      12
      46 npm
      MIT

    • MCPSaver

      cpntodd
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for persistent, searchable agent memory using SQLite FTS5, replacing flat MEMORY.md files with efficient full-text search and workspace context caching.
      GPL 3.0
    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 6 tools

    Disambiguation5/5

    Each tool has a distinct, clearly described purpose: recording events, reading state, searching, applying operations, viewing history, and reading patches. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent 'memory_verb_noun' pattern (e.g., memory_record_event, memory_search, memory_patch_read), ensuring predictability.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a memory patching system—covers core operations without unnecessary bloat or deficiency.

    Completeness4/5

    Covers recording, reading, searching, applying (add/update/supersede/remove), history, and patch details. Minor gaps: no explicit rollback or full patch listing, but core workflow is solid.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources