Skip to main content
Glama
Sign In
telemem

telemem

by TeleAI-UAGI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to telemem

No user-submitted related servers found.

    Related Servers

    • local-memory

      Sergey-Vladimirovich-Hankok
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to keep durable long-term memory on the user's own machine, writing sessions and messages into a local SQLite database and retrieving them via keyword, exact, or optional semantic search with surrounding context. Runs entirely offline over stdio, so no cloud service or API key is required to give an agent recall across sessions.
      1
      MIT

    • 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

    • MemStack MCP Server

      a847840750
      A
      license
      B
      quality
      C
      maintenance
      Exposes 12 memory and multi-agent tools over stdio JSON-RPC so agents can write episodes and extracted facts, then recall them with hybrid retrieval, bi-temporal state tracking, and evidence-chain decomposition under a token budget. It also supports agent registration, team-shared memory with access grants, and an event bus for multi-agent collaboration.
      12
      Apache 2.0

    • Agent Memory Engine

      rgolabs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.
      10 npm
      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
    ResponsivenessUsually handled

    Resources