Skip to main content
Glama
Sign In
memanto-mcp

memanto-mcp

by geoffsdesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to memanto-mcp

No user-submitted related servers found.

    Related Servers

    • Recall

      Greco86321
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other AI agents to store and automatically retrieve persistent memories across sessions, surviving restarts and context compaction. Supports self-hosting on Redis/Valkey or a managed SaaS, with workspace organization and semantic search.
      24 npm
      MIT

    • Kronvex

      Daftgoldens
      A
      license
      A
      quality
      D
      maintenance
      Persistent memory API for AI agents — store, recall, and inject semantically-searchable context across sessions. EU-hosted, GDPR-compliant. Supports Claude, Cursor, Cline, and any MCP-compatible client.
      4
      2
      MIT

    • Recall

      francescoburke69422
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and AI agents to store and automatically retrieve memories across sessions, surviving context limits and restarts. Supports self-hosted Redis/Valkey or a managed cloud service with workspace organization and semantic search.
      24 npm
      MIT

    • Recall

      bKarabacak65
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other AI agents to store and retrieve decisions, patterns, and knowledge persistently across sessions and context compaction, either self-hosted on Redis/Valkey or through a managed SaaS.
      24 npm
      MIT

    • engram

      devinmlowe
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other LLM agents to capture, consolidate, and retrieve memories from conversation history, building a local-first knowledge graph with semantic search and dream-state consolidation.
      63 npm
      1
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation3/5

    The forget/remember/recall core is clear, but three retrieval tools (recall, recall_as_of, recall_current) overlap: the docs never state whether plain `recall` already excludes superseded memories, and recall_as_of/recall_current document no agent_id or filter args, so an agent cannot tell whether they are scoped per-agent or global. The remember-vs-answer split (raw storage vs synthesized RAG) is well delineated.

    Naming Consistency5/5

    Every tool uses the same `memanto_` prefix with a snake_case verb or verb_object form (remember, recall, answer, create_agent, list_agents, get_agent, delete_agent). The recall_* variants form a predictable modifier pattern rather than a convention break.

    Tool Count5/5

    Nine tools is well-scoped: five memory operations plus four agent lifecycle operations, each earning its place. No obvious filler tools or redundancies that would bloat the surface.

    Completeness3/5

    Agent management is full CRUD except update_agent, but the memory lifecycle is write-and-read only — there is no way to update, forget, delete, or supersede an individual memory, despite memory types like 'error' and 'commitment' implying correction workflows. recall_as_of and recall_current also lack documented parameters, leaving dead ends for filtered use.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources