Skip to main content
Glama
蓝汐 · 潮汐认知图谱

蓝汐 · 潮汐认知图谱

by A16Nights

Related Servers

Alternatives to 蓝汐 · 潮汐认知图谱

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI agents a durable, locally hosted temporal memory built from a markdown vault you own, exposing hybrid semantic/lexical/entity search over events, threads, transcripts, entity relationships with validity dates, and patterns with confidence decay. Writes are approval-gated, so agents can draft, commit, and sync new memories while keeping every index rebuildable and nothing leaving your machine.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to maintain a persistent, queryable memory stored as user-owned Markdown files, with dual-channel retrieval (FTS5 and optional semantic search) and an audited write pipeline.
      11
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent long-term memory for AI assistants with tag-based retrieval, wiki-style linking, and source references, storing memories as markdown files with SQLite index.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to write, search, browse, link, consolidate, and promote layered Markdown-backed memories with SQLite FTS5 indexing, rule checks, and optional semantic retrieval across projects.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents like Codex, Grok Build, and Antigravity to share persistent local memory, preferences, project context, tasks, and handoffs using Markdown and SQLite.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and retrieve from a local Markdown-native persistent memory vault through an MCP recall tool, using a knowledge graph with learned retrieval and decay.
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Core operations are clearly separated: cg_read/cg_write/cg_update/cg_recall/cg_link/cg_graph each target a distinct action on the memory graph. The main soft spot is the cluster of node-creation tools (cg_write, cg_goal, cg_reflect, cg_import_vault), which all produce nodes and are distinguished mainly by which layer they default to rather than by a fundamentally different operation. cg_stats vs cg_maintain(queue) also border on overlapping, though the descriptions clarify the read-only overview versus maintenance-queue split.

    Naming Consistency4/5

    Every tool uses the same cg_ prefix and snake_case, giving a predictable family identity. However the stems mix verbs (cg_read, cg_write, cg_forget, cg_link, cg_recall, cg_reflect, cg_maintain) with bare nouns (cg_stats, cg_graph, cg_goal), and cg_import_vault is the lone two-word stem. Readable and mostly predictable, but not a single uniform convention.

    Tool Count5/5

    Twelve tools is well within the comfortable range for a memory-graph server and each tool maps to a recognizable lifecycle operation. The maintain tool bundles eight sub-actions into one entry point, which keeps the surface lean rather than bloating it with near-duplicate maintenance verbs.

    Completeness4/5

    The lifecycle is largely covered: create, read, update, recall/search, link, subgraph traversal, goals, reflection, stats, import, and maintenance. Notable gaps include no way to remove or retype an existing edge (cg_link exists but there is no unlink/relink), and no explicit bulk list/enumerate-nodes or export path outside recall. These are workable gaps rather than dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues