Grafyx
Related Servers
Alternatives to Grafyx
- AlicenseBqualityAmaintenanceAn MCP code-intelligence server for AI agents with pre-indexed AST cache, 62 MCP tools, and TOON-compressed output, enabling token-efficient code analysis and project health grading entirely locally.9815 PyPI50MIT
Related Servers

NEAT MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceProvides AI agents with a live architecture model of a codebase, enabling queries for root cause analysis, blast radius, and dependency traversal through MCP tools.175 npm20Apache 2.0- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with a structured, token-efficient map of a codebase's symbols, dependencies, and relationships via MCP tools like overview, query, and impact analysis.8MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI agents with a function-level dependency graph of the codebase through 30 MCP tools, enabling structural queries about code dependencies, callers, and impact analysis.1,555 npm95Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides code intelligence for AI coding agents by indexing repositories into a hybrid knowledge graph, enabling agents to query dependencies, impact, and context through 28 MCP tools.3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides AI-powered architecture analysis and visualization of codebases, exposing 17 MCP tools for querying components, dependencies, and generating interactive diagrams.602 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.14 npm3MIT
TDQS
Scored across 14 tools
Most tools are clearly scoped by level (project, module, file, function, class). Two pairs have conceptual overlap — find_related_code/find_related_files and get_dependency_graph/get_call_graph — but their descriptions clarify different output types (symbols vs files; dependencies vs call chains). Slight ambiguity remains when choosing between the graph tools for a function.
All 14 tools use lowercase verb_noun snake_case, with verbs limited to get/find/set/refresh. The pattern is consistent and predictable.
14 tools is within the ideal 3–15 range and each tool addresses a distinct analysis need, from setup (set_project) to refresh, to various context scopes and relationship queries. No tool feels unnecessary.
The server covers the full code-understanding lifecycle: set project, refresh graph, view skeleton, drill into modules/files/functions/classes, find related items, explore dependencies/calls, check conventions, and detect dead code/unused symbols. The only minor gap is a direct search-by-symbol-name tool, but find_related_code covers conceptual lookup.