Skip to main content
Glama

Related Servers

Alternatives to apex-memory

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for managing a local, domain-agnostic knowledge base using Markdown notes with frontmatter. Enables AI agents to capture, read, search, link, and maintain notes with atomic writes and privacy controls.
      13
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Markdown + SQLite knowledge store with bidirectional wikilinks, exposed as an MCP server for AI agents to maintain an interconnected knowledge base.
      11
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables creating, linking, searching, exploring, and synthesizing atomic notes as a knowledge graph through MCP-compatible clients such as Claude. Supports tags, note types, semantic relationships, Markdown storage, and an SQLite index for efficient traversal.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients such as Claude to create, link, search, explore, and synthesize atomic notes using a Markdown source of truth with an SQLite index for traversal and querying.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, read, ingest, annotate, and manage a self-hosted knowledge base of archived links, Git repositories, documents, and notes over MCP.
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Provides AI agents with a local, private Markdown-based memory vault and SQLite search. Enables agents to search, read, list, and traverse linked knowledge pages via MCP with zero external runtime dependencies.
      7
      33 PyPI
      9
      MIT

    TDQS

    A3.6/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: read vs search, patch_section vs patch_header, log_query vs log_append, lease vs batch all differ in scope. Some residual overlap: patch_header's decision status field vs set_decision_status's Status line, and batch vs individual write tools could confuse an agent about which path to use. Descriptions are highly detailed and largely disambiguate these.

    Naming Consistency3/5

    Mixed conventions: bare verbs (move, brief, read, search, check, batch), verb_noun (log_query, patch_section, create_note, set_decision_status, create_domain, list_domains), and bare nouns (links, preference, source, lease, status_item). All are readable and snake_case throughout, but there is no single predictable pattern.

    Tool Count4/5

    19 tools is at the upper end for what the domain needs, but each maps to a distinct capability (notes, sections, headers, links, log, status, decisions, sources, preferences, leases, checks, batch). Nothing appears gratuitous, though the surface is slightly heavy.

    Completeness4/5

    Coverage is broad: create/read/update for notes, sections, headers, status items, decisions, sources and domains, plus search, links, log and validation. The notable gap is deletion/archival (no delete_note, delete_domain or link removal beyond uncite), which may be intentional for an auditable memory store but limits lifecycle completeness.