Skip to main content
Glama

Related Servers

Alternatives to AgenticSystemCore

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search, record, correct, and review the provenance and version history of memories, and to obtain answers composed from guarded context in which private values are replaced by placeholders and resolved locally on the device. Exposes these capabilities through dependency-free tools over stdio.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local research vault over stdio: search, read and link the markdown notes a Claude Code or Codex deep-research pipeline collected, list and check sources, and fetch new URLs into the vault.
      548 PyPI
      4,454
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a living systems memory vault to autonomous agents, letting them search notes with BM25 ranking, read sections within token budgets, extract API/port/schema contracts, compute dependency blast radius, and run machine-verifiable invariant assertions before mutating code. It also supports surgical frontmatter edits, schema linting, wikilink integrity checks, and worklog recording, over stdio MCP.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search, read, stage candidate memories, and inspect vault status against a local Markdown-based memory vault over stdio.
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Local Markdown-backed memory tools for Codex and other MCP-capable agents. Exposes durable agent knowledge via CLI and MCP server.
      5
      MIT

    TDQS

    B3/5.0

    Scored across 7 tools

    Disambiguation3/5

    Two pairs overlap meaningfully: ask vs search both retrieve items (differing mainly in whether a model/description output is used), and propose vs remember both return Proposal payloads (one retrieves an existing payload, one synthesizes a draft). read/links/compose are clearly distinct, and descriptions do clarify the boundaries, but an agent could still misselect within the retrieval and proposal pairs.

    Naming Consistency4/5

    Nearly all tools are single lowercase verbs (ask, compose, propose, read, remember, search), giving a predictable style. The lone outlier is 'links', a noun that names a resource rather than an action, a minor deviation from an otherwise consistent convention.

    Tool Count5/5

    Seven tools is a well-scoped set for a memory/knowledge core, covering retrieval, traversal, composition, and proposal drafting without redundancy. Each tool has a plausible distinct role in the workflow.

    Completeness3/5

    Query and draft coverage is good (read, search, ask, links, compose, remember, propose), but the surface stops at proposals: both propose and remember explicitly perform no write, and there is no apply/commit tool or any update/delete of existing items. Agents can draft but cannot persist changes, a notable lifecycle gap.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues