Skip to main content
Glama
CODYNEX Engine

CODYNEX Engine

Related Servers

Alternatives to CODYNEX Engine

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives coding agents local software intelligence: it surfaces the files, tests, and helpers relevant to a task before edits, flags missed callers and uncovered code during review, and returns a single SHIP / NOT PROVEN / NO-SHIP verdict when the agent stops. Everything runs on the local index with no network calls, so repository code stays on the machine.
      3,833 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Live codebase intelligence for AI agents. Import graph PageRank for file importance, git forensics for co-change coupling and fragile code, convention detection across 16 domains, and blast radius analysis.
      21 npm
      3
      Business Source 1.1
    • A
      license
      B
      quality
      B
      maintenance
      Indexes a Python/JS/TS repository into a local SQLite knowledge graph so agents can trace callers, callees, imports, subclasses and covering tests, measure impact radius, rank diff risk, and summarize architecture without grepping files. Exposes these queries as MCP tools alongside an equivalent CLI, with no daemon, embeddings, or network access.
      10
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to index local Python repositories and retrieve code intelligence through semantic search, caller lookups, hybrid context expansion, and visualization.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents and developers to search code by meaning and exact text, map symbols, dependencies, blast radius and context, inspect git-change impacts, and trace live Python or JavaScript execution from a local air-gapped SQLite index.
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct capability: architecture summary, component impact, historical decisions, and request-level change planning. No two tools overlap in input or output scope, so an agent can easily select the right one.

    Naming Consistency5/5

    All four tools use the dna_ prefix followed by a single noun (map, impact, decisions, plan), forming a consistent and predictable naming convention.

    Tool Count5/5

    Four tools are well-suited for a focused architecture analysis engine; each covers a unique analysis dimension without redundancy.

    Completeness4/5

    The set covers key analysis outputs (summary, impact, decisions, plan) but lacks a tool to ingest/refresh the project or drill into specific components/decisions, leaving minor workflow gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues