Skip to main content
Glama
MyAI4

Anamnesis MCP

by MyAI4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Anamnesis MCP

No user-submitted related servers found.

    Related Servers

    • Memory MCP

      EtienneBBeaulac
      A
      license
      A
      quality
      C
      maintenance
      Gives AI coding agents persistent, evolving knowledge about a codebase, enabling them to store and retrieve observations about architecture, conventions, gotchas, and recent work context.
      10
      40 npm
      2
      MIT

    • 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.
      8 npm
      2
      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.
      26 npm
      MIT

    • arcane

      Edition-X
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent, searchable memory and knowledge capture for AI-assisted development, enabling agents to retain decisions, bugs, and patterns across sessions and projects.
      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

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct role in a clear import-then-recall pipeline (scan → split → fetch → create_memory, plus recall/search/ping). The only mild overlap is anamnesis_recall vs anamnesis_search, but the descriptions clearly differentiate semantic vs keyword/tag lookup.

    Naming Consistency4/5

    All tools share the anamnesis_ prefix and use a verb_noun pattern (fetch_source, scan_sources, split_source, create_memory). Minor deviations are the single-word ping and recall/search, which are still readable and consistent in style.

    Tool Count5/5

    Seven tools is well-scoped for a memory store: a coherent import pipeline plus retrieval and a health check, with each tool earning its place and no redundancy.

    Completeness3/5

    The ingest-and-retrieve lifecycle is largely covered, but memory lifecycle operations are missing—no update_memory, delete_memory, or fetch_memory-by-id—so agents cannot correct or prune stored memories. These are notable gaps, though the core workflow still functions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources