Skip to main content
Glama

Related Servers

Alternatives to aoci-code

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to query a locally indexed structural code graph — source entities, callers/callees, Git relationships and recorded mistakes — so they retrieve focused, token-bounded context instead of reading entire files. It runs over local SQLite and can be served through a CLI, agent hooks, an MCP executable and an authenticated local dashboard.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local-first codebase intelligence layer for AI coding agents, providing a persistent, queryable model of a repository via an MCP server and CLI to enable structure queries instead of reading many files.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Zero-dependency Go MCP server that indexes codebases into an embedded Kùzu graph DB—enabling 90%+ token reduction, precise call-chain queries, and AI architectural health audits.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Local-first codebase intelligence engine providing AI coding agents with a typed MCP toolset for understanding and navigating code repositories.
      100
      54
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first repository memory for AI coding agents that indexes codebases into SQLite and exposes it through MCP tools, with a browser dashboard for architecture inspection.
      2 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation3/5

    The tools cover distinct actions, but the read surface has meaningful overlap: aoci_overview, aoci_get_entries, and aoci_search all retrieve cognition content, and aoci_header versus aoci_rules both expose governing rules. The very elaborate descriptions repeatedly try to prevent misuse, which helps but also signals that the boundaries are not naturally obvious.

    Naming Consistency4/5

    All tools share the aoci_ prefix and are readable in snake_case. The suffix pattern is mostly action-oriented, but aoci_header, aoci_overview, and aoci_rules are noun-style rather than verb_noun, so it is not perfectly consistent.

    Tool Count5/5

    Nine tools is well within a reasonable range for a cognition/index governance server. Each tool maps to a recognizable operation: read overview, search, get entries, read rules/header, maintain, update, remove, and report.

    Completeness4/5

    The surface covers the core lifecycle: orientation via header/rules, reading via overview/search/get_entries, authoring via maintain/update_entry, orphan removal, and reporting. Some referenced workflow concepts such as Verify, Check, and Guide are not exposed as first-class tools, but the main governance path appears workable.