Skip to main content
Glama
TeleAI-UAGI

telemem

by TeleAI-UAGI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to telemem

No user-submitted related servers found.

    Related Servers

    • engram-mcp

      Cartisien
      A
      license
      A
      quality
      C
      maintenance
      Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings with keyword fallback. Tools: remember, recall, history, forget, stats.
      17
      37 npm
      1
      MIT

    • lean-memory

      Wuesteon
      A
      license
      A
      quality
      A
      maintenance
      Embedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.
      7
      42
      Apache 2.0
    • deepmem by deepmemteam

      deepmemofficial

      deepmemteam
      A
      license
      Not graded
      quality
      C
      maintenance
      Mem0-compatible persistent memory for AI agents - write facts once, recall them semantically in any session. Self-hostable open-source server, or managed cloud with a remote MCP endpoint at https://deepmem.dev/mcp.
      114
      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.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct role: add, get, search, list, update, delete, delete-all, and history. No overlaps or ambiguity; the descriptions clarify the differences between get_memory and get_memories.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern (add_memory, get_memory, search_memories, update_memory, delete_memory). The exception is memory_history, which is noun_noun, breaking the pattern slightly.

    Tool Count5/5

    The 8 tools cover the full memory lifecycle without bloat. The count is appropriate for a specialized memory server, neither sparse nor excessive.

    Completeness5/5

    The surface covers the complete CRUD spectrum (add, get, update, delete), plus listing, semantic search, delete-all for scope cleanup, and history tracking. No obvious gaps for the stated purpose of long-term memory management.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources