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
- FlicenseAqualityBmaintenanceA persistent, Git-versioned map of your whole codebase and database schema that coding agents read before they touch anything. Local-first MCP server + CLI in Go: a governed repository index of code knowledge that gives Claude Code, Codex, Cursor, and opencode long-term context, memory, and code intelligence.91,872-
- 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.7Apache 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
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.56 PyPI4MIT
- 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 gradedqualityDmaintenanceA 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.1,023 PyPI816MIT
TDQS
Scored across 69 tools
The set covers many distinct static-analysis questions and most descriptions include explicit WHEN TO USE / NOT TO USE guidance, which helps agents choose correctly. However, there are real overlaps: gograph_trace is an alias of gograph_errorflow, gograph_mocks duplicates gograph_implementers(test_only=true), and context/explore/explain/plan plus summary-versus-individual-metrics tools require careful reading to select. The large surface amplifies misselection risk.
All tools use a predictable gograph_ prefix with snake_case, with no mixed camelCase or chaotic conventions. Most names are domain nouns rather than strict verb_noun, and a few use suffix verbs such as boundaries_create and session_create, but the convention remains readable and consistent.
With 69 tools, the server is far beyond the 3-15 well-scoped range and exceeds the 50+ extreme threshold. Even for a broad Go graph-analysis domain, the surface is heavily bloated with aliases, aggregate tools, and fine-grained variants that could be consolidated.
The surface covers call graphs, package dependencies, structs/interfaces, tests and coverage, HTTP routes, SQL, environment variables, errors, concurrency, complexity, architecture boundaries, API drift, change/risk/review workflows, sessions, and wiki generation. For the static-analysis domain, the lifecycle of querying and reporting is comprehensively covered.