Skip to main content
Glama
AQuietRiver

Local Memory MCP

by AQuietRiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Local Memory MCP

No user-submitted related servers found.

    Related Servers

    • moss-brain

      Naut1cal5
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides semantic memory with search, related-content traversal, and write-back capabilities, all powered by local embeddings of your notes, documents, and chat histories.
      3
      MIT

    • mesh-memory

      dklymentiev
      A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).
      1
      MIT

    • Memento

      iAchilles
      A
      license
      A
      quality
      C
      maintenance
      A local, fully-offline MCP memory server that enables persistent storage and retrieval of information using SQLite with both keyword and semantic vector search capabilities.
      10
      15 npm
      13
      MIT

    • light-agent-memory-mcp-server

      AliYar-Khan
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.
      12
      12 npm
      MIT

    • vault-vector

      All-zen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables semantic and full-text search over markdown notes, with tools to create, edit, move, and delete notes, all through MCP. Runs entirely locally using Ollama for embeddings and SQLite for storage, working with Obsidian or standalone.
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: search retrieves, store adds, wipe deletes. No ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (search_memory, store_memory, wipe_project_memories).

    Tool Count5/5

    3 tools cover the core operations for a local memory server (search, store, delete). The count is well-scoped and earns its place.

    Completeness4/5

    The set covers essential memory operations, but lacks an update or list tool. However, delete+re-store can update, and search serves as discovery. Minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources