Audrey
Related Servers
Alternatives to Audrey
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceLocal-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.2Apache 2.0
- AlicenseCqualityAmaintenanceLocal-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.4055 PyPI1MIT
- AlicenseAqualityFmaintenanceLocal-first MCP memory server that gives AI coding agents long-term memory via SQLite and sqlite-vec, with optional LLM-powered layering. No gateway or API key required.7126 npm4MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.1 npm1Apache 2.0
- AlicenseBqualityAmaintenanceLocal-first, auditable memory for Codex, Claude Code, and MCP clients. It stores scoped user/project memory in SQLite or Postgres, serves read-only recall and inspection tools by default, and supports opt-in governed writeback with review and forget controls.8145 npm18MIT
- AlicenseNot gradedqualityBmaintenancePersistent memory MCP server for AI agents, featuring a visual interface to browse, search, edit, and delete memory. It provides tools for capturing episodes, recalling, consolidating, crystallizing traits, and forgetting, with local SQLite storage and optional authenticated web UI.MIT
TDQS
Scored across 23 tools
All tools share the memory_ prefix and many names describe overlapping cognitive operations (e.g., memory_consolidate, memory_reflect, memory_dream, memory_encode, memory_recall, memory_introspect) with no descriptions to clarify boundaries. An agent would struggle to choose between several of these tools.
Every tool follows the exact snake_case memory_<verb> pattern with a clear prefix and action verb. The naming convention is perfectly consistent across all 23 tools.
23 tools is on the heavy side for a single server, even for a memory-focused domain. The count is manageable but begins to feel bloated, especially with many near-synonymous operations.
Without descriptions, the intended domain is only inferable from names, which suggest a memory lifecycle. Obvious operations like search/list or a clear memory store are absent, while many speculative tools (memory_dream, memory_greeting, memory_capsule) exist, creating significant gaps in a coherent surface.