Skip to main content
Glama
tinhien11

tdai-memory-mcp

by tinhien11

Related Servers

Alternatives to tdai-memory-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory for AI coding agents. Enables agents to save and recall decisions, patterns, bugs, and context across sessions via an MCP server with local SQLite storage.
      14 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Local-first cross-agent memory for AI coding agents. Persistent, shared memory over MCP — what you tell one agent can be recalled by another — with all data stored in a single local SQLite file, no cloud and no API keys.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server providing persistent, layered memory (episodic, semantic, procedural, resource) for AI agents, with search, versioning, and session management via a single SQLite file.
      54 npm
      3
      MIT
    • 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.
      288 PyPI
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing persistent AI memory with four-tier retrieval (SQLite FTS5, graph, vector, LLM agent) to give AI assistants structured, long-term memory without RAG.
      1
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: recall for broad context, search for specific facts, capture for saving, resolve for conflicts, forget for deletion, handoff for session transfer, and adr for architecture decisions. The main overlap is between recall and search, but their descriptions clarify the difference (broad versus specific).

    Naming Consistency4/5

    Tool names are mostly single-word lowercase verbs (recall, capture, search, resolve, forget), which forms a predictable pattern. However, 'handoff' is a noun/phrasal verb and 'adr' is an acronym, creating minor deviations from the otherwise consistent verb style.

    Tool Count5/5

    With 7 tools, the set is well-scoped for a memory-management server. Each tool serves a distinct memory lifecycle function without unnecessary bloat or overlap.

    Completeness4/5

    The tool surface covers core memory operations: store (capture), retrieve (recall/search), delete (forget), conflict handling (resolve), plus specialized features (handoff, adr). A missing explicit 'update memory' tool is a minor gap, but capture can serve that role implicitly.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues