Skip to main content
Glama

Related Servers

Alternatives to code-explorer

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    Indexes a mono-repo into a knowledge graph and provides MCP tools to query code structure—packages, components, routes, HTTP calls—without file reads or grep round-trips.
    7
    22 npm
    MIT
  • 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
    Not graded
    quality
    B
    maintenance
    Provides AI agents with a live architecture model of a codebase, enabling queries for root cause analysis, blast radius, and dependency traversal through MCP tools.
    263 npm
    33
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Local-first MCP server that scans a repository once and answers architecture questions from an evidence-backed graph, enabling dependency analysis, impact analysis, and codebase exploration without re-reading the source tree.
    7
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Dev intelligence layer that builds a knowledge graph from any codebase and exposes 7 MCP tools for graph-powered reasoning, impact analysis, and preflight safety and governance checks.
    301 PyPI
    32
    Apache 2.0
  • A
    license
    A
    quality
    A
    maintenance
    Framework-aware code intelligence MCP server that builds a cross-language dependency graph from source code. 53 integrations (Laravel, Django, Rails, Spring, NestJS, Next.js, and more) across 68 languages. 100+ tools for navigation, impact analysis, refactoring, security scanning, session memory, and CI/PR reports — up to 97% token reduction.
    29
    3,709 npm
    203
    MIT

TDQS

B3/5.0

Scored across 33 tools

Disambiguation3/5

Most tools have distinct graph-analysis purposes, but several clusters overlap heavily: get_architecture_view, get_architecture_map, and get_architecture_overview are easy to confuse, as are get_call_chain, get_callers, analyze_code_impact, and trace_cross_service_flow. The descriptions provide useful distinctions, but an agent still has to reason carefully to choose the right architecture or call-analysis tool.

Naming Consistency5/5

All tool names use consistent snake_case verb_noun conventions such as get_callers, find_symbol, scan_workspace, and execute_project_query. The pattern is predictable throughout, even across the large surface.

Tool Count2/5

33 tools is heavy for a code graph explorer and includes many closely related architecture, call-analysis, and semantic-gate tools. While the domain is complex, several tools could likely be consolidated or exposed through a smaller, clearer set.

Completeness4/5

The surface covers workspace lifecycle, indexing, schema inspection, symbol search, call graphs, impact analysis, test coverage, architecture views, service contracts, data lineage, and semantic gates. Minor gaps exist around updating or deleting custom graph data and managing saved queries beyond save/list/execute, but core exploration workflows are well covered.

Maintenance

ActivityActive
ResponsivenessUsually handled