Skip to main content
Glama
809179409-bot

anchor-memory

by 809179409-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to anchor-memory

No user-submitted related servers found.

    Related Servers

    • arcane

      Edition-X
      A
      license
      Not graded
      quality
      B
      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

    • open-zk-kb

      mrosnerr
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI assistants persistent, shared memory using the Zettelkasten method, so they retain corrections, preferences, and decisions across sessions and across tools via local, hybrid search.
      1,080 npm
      7
      MIT

    • saripati

      kyouscireul
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI assistants a local, hybrid semantic+keyword memory vault to save research findings, notes, and project context, and recall them across sessions with session boot/save tools.
      36 npm
      2
      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.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating, searching, reviewing, deleting cards, logging topics, importing/claiming packs, and generating reports. No two tools overlap in function or trigger condition.

    Naming Consistency4/5

    Tools follow a consistent snake_case, mostly verb_noun pattern (save_card, search_cards, review_card). 'due_cards' uses an adjective-led name instead of a verb, a minor deviation from the otherwise uniform convention.

    Tool Count5/5

    9 tools cover the full memory workflow without redundancy: create, retrieve, review, delete, log, import, claim, and analyze. The count feels intentional and well-scoped for the domain.

    Completeness4/5

    The core card lifecycle is complete (create, search, review, delete) plus useful extras like packs, logs, and reporting. Minor gaps exist, such as no direct edit-card tool or explicit pack management beyond claiming, but these don't break the main workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources