Skip to main content
Glama
Sign In
Smara Memory MCP Server

Smara Memory MCP Server

by smara-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Smara Memory MCP Server

No user-submitted related servers found.

    Related Servers

    • Mnemex

      prefrontal-systems
      A
      license
      A
      quality
      D
      maintenance
      Provides human-like memory dynamics for AI assistants where memories naturally fade over time unless reinforced through use, mimicking the Ebbinghaus forgetting curve. Enables automatic saving, searching, and management of contextual information with temporal decay algorithms.
      11
      39
      AGPL 3.0

    • recall-mcp

      eddyflores100-lang
      A
      license
      A
      quality
      C
      maintenance
      Provides persistent, cross-session memory for AI agents, letting them store, search, and manage memories with tools like remember, recall, forget, list, summarize, and import/export.
      8
      MIT

    • MCP-Mem0

      Baatarvant
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI agents with persistent long-term memory capabilities using semantic search. Enables storing, retrieving, and searching memories through three core tools integrated with Mem0 and vector storage.
      MIT

    • engram

      HalisAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to keep a durable, local-first long-term memory in a single SQLite file, where frequently recalled facts strengthen and unused traces decay, with sleep-time consolidation that merges duplicates and distills episodes into semantic gists. Exposes six tools — remember, recall, context, forget, dream, and stats — so clients can store facts, pull prompt-ready memory blocks, and permanently erase data on request.
      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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap. For example, 'list_memories' shows stored memories, 'search_memories' performs semantic search, 'store_memory' creates new memories, 'update_memory' modifies existing ones, 'delete_memory' removes memories, 'get_user_context' retrieves formatted context, and 'get_usage' monitors system usage. The descriptions reinforce these unique roles, eliminating any ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as 'list_memories', 'search_memories', 'store_memory', 'update_memory', 'delete_memory', 'get_user_context', and 'get_usage'. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count5/5

    With 7 tools, this server is well-scoped for a memory management system. The count is appropriate as it covers essential operations like CRUD (create, read, update, delete), search, context retrieval, and usage monitoring without being excessive or insufficient. Each tool serves a clear, necessary function in the domain.

    Completeness5/5

    The tool set provides complete coverage for memory management, including storing, listing, searching, updating, deleting, retrieving context, and monitoring usage. There are no obvious gaps; it supports full lifecycle management from creation to deletion, with additional utilities for context and system health, ensuring agents can handle all typical workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources