gograph
Related Servers
Alternatives to gograph
- AlicenseNot gradedqualityDmaintenanceAn MCP server that transforms codebases into knowledge graphs using Neo4J, enabling AI assistants to understand code structure, relationships, and metrics for more context-aware assistance.28MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceA local code-intelligence engine for AI agents that indexes repositories into a PostgreSQL-backed code graph and serves structured, token-budgeted context over MCP and HTTP, enabling targeted queries on symbols, dependencies, contracts, and impact analysis.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceZero-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.1MIT
- FlicenseNot gradedqualityDmaintenanceA minimalist indexing tool that provides AI agents with semantic search and structural AST parsing for deep codebase understanding. It enables autonomous agents to navigate large codebases predictably using vector embeddings and native language server capabilities like definition and reference tracking.-
- AlicenseNot gradedqualityCmaintenanceA graph-powered code intelligence engine that indexes codebases into a structural knowledge graph to provide AI agents with deep context on function calls, types, and execution flows. It offers local, zero-dependency tools for hybrid search, impact analysis, and dead code detection across Python, JavaScript, and TypeScript projects.956 PyPI814MIT
- FlicenseNot gradedqualityAmaintenanceProvides efficient code navigation and graph-based analysis for AI agents, enabling symbol resolution, callers, implementations, and type schemas with minimal token usage.-
- AlicenseNot gradedqualityAmaintenanceProvides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.4,912 npm4MIT
TDQS
Scored across 67 tools
Most query tools have sharply distinct semantics (one-hop vs transitive, fan-in vs fan-out, upstream vs downstream), and the exhaustive WHEN TO USE / NOT TO USE cross-references make selection tractable even at this scale. The main blemishes are deliberate duplicates — gograph_trace as a straight alias of gograph_errorflow and gograph_mocks duplicating gograph_implementers(test_only=true) — plus subtle boundaries between aggregate tools (gograph_context vs gograph_explain, gograph_plan vs gograph_review vs gograph_risk) that an agent could conflate.
All 67 tools follow a uniform gograph_ prefix with concise single-word noun names for queries (arity, callers, godobj, returnusage), and multi-word names consistently use underscores with no camelCase mixing. Session lifecycle tools use gograph_session_ + verb (create, end, audit, cleanup) and gograph_boundaries_create pairs cleanly with gograph_boundaries, so the pattern is highly predictable.
67 tools far exceeds the well-scoped 3-15 range and will tax context windows and agent tool-selection even with orientation helpers like gograph_capabilities and gograph_summary. The domain is genuinely broad — call graphs, package deps, code smells, HTTP, SQL, env, concurrency, tests, security, sessions, wiki generation — so it is not a total mismatch, but aliases, aggregators, and auxiliary session/wiki/meta tools create obvious consolidation opportunities that could cut the surface by roughly half.
The tool set maps the entire static-analysis space: call/package/type graph queries, code smells, HTTP routes and endpoint slices, SQL, env vars, error propagation, concurrency sites, security flow, test attribution and untested sweeps, API drift, and pre/post-edit workflow support. Documented exclusions (running tests, runtime coverage proof, external module versions) are explicitly stated as out of scope, and every concern has both a discovery entry point and a drill-down path.