Skip to main content
Glama
NBibikov

cogvault

by NBibikov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cogvault

No user-submitted related servers found.

    Related Servers

    • memory

      go-ports
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides coding agents with persistent local memory by exposing tools to save, search, and retrieve decisions, bugs, and context as Markdown with hybrid keyword and semantic search.
      4
      MIT

    • Remnic

      joshuaswarren
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first memory for AI agents: one store shared by Claude Code, Codex CLI, Cursor, Pi, Hermes, OpenClaw, and any MCP client. Plain markdown with YAML frontmatter on your disk, hybrid BM25 + vector recall with per-result provenance (Recall X-ray), a correction contract, and the MemCorrect benchmark.
      229
      MIT

    • auxly-memory-cli

      Tzamun-Arabia-IT-Co
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
      2
      MIT

    • Link

      gowtham0992
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.
      218
      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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are perfectly complementary: cogvault_recall is read/search and cogvault_record is write/save. There is no overlap, and the descriptions make the read-before-write workflow explicit, so an agent can never confuse them.

    Naming Consistency5/5

    Both names follow the same predictable pattern of a namespace prefix plus a clear verb (cogvault_recall, cogvault_record). This is a consistent, readable convention with no deviations.

    Tool Count3/5

    Two tools is the bare minimum for a persistent memory store covering store and retrieve. It is borderline thin; a memory service realistically needs at least update/delete/forget to feel well-scoped.

    Completeness3/5

    The core save-and-search lifecycle is covered, but there is no way to update, correct, or delete a memory card once recorded, and no listing or browsing operation. These are notable gaps that could force agents to rely on superseding stale cards.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources