Skip to main content
Glama
tt-a1i

evermemos-mcp

by tt-a1i
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to evermemos-mcp

No user-submitted related servers found.

    Related Servers

    • Heimdall MCP Server

      lcbcFoo
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent, context-rich memory of a codebase, including documentation and git history, enabling recall across sessions.
      104
      Apache 2.0

    • amem

      amanasmuei
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent memory for AI coding tools, allowing them to remember corrections, decisions, and preferences across sessions and different tools.
      60
      2
      MIT

    • evermemos-mcp-server

      wyh0626
      A
      license
      A
      quality
      D
      maintenance
      Enables AI coding assistants to store and retrieve persistent long-term memory across sessions, remembering project preferences, build steps, and architecture decisions.
      4
      MIT

    • ShackleAI Memory MCP

      shackleai
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory for AI coding tools, enabling AI assistants to store and recall project decisions, conventions, and context across sessions.
      82
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a specific role: discovery, storage, status check, search, briefing, deletion, and history. The retrieval tools (recall, fetch_history, briefing) overlap somewhat, but their descriptions clearly distinguish relevance search, chronological paging, and structured summaries.

    Naming Consistency4/5

    Most tool names follow a verb or verb_noun pattern (list_spaces, remember, request_status, recall, forget, fetch_history). 'briefing' is a noun-only deviation, breaking the otherwise consistent style.

    Tool Count5/5

    Seven tools is well-scoped for a memory management server, covering discovery, write, status, search, summary, delete, and history without being bloated.

    Completeness3/5

    Core operations are covered (create, read, search, delete, list), but there is no explicit update tool, and 'remember' references a nonexistent 'check_conflicts' tool. Minor gaps exist around memory editing and conflict handling.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources