project-graph-mcp
Related Servers
Alternatives to project-graph-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to reduce token usage by condensing source code into AST skeletons, extracting specific symbols, compressing logs, and estimating token budgets.4MIT
- AlicenseNot gradedqualityBmaintenanceReduces token consumption for AI coding agents by 50-70% through intelligent code context filtering, Git delta tracking, and local SQLite/Tree-sitter indexing.167 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to compress terminal output and file context in real time, preserving full error tracebacks while reducing token consumption by 60-85%.43MIT

Code Scalpelofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to surgically extract and analyze code, reducing token usage and costs by up to 200x compared to reading entire files.18MIT- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to quickly find relevant code, focus reads on important parts of large files, and pick relevant items from long lists, reducing token usage and search time.7MIT
- FlicenseAqualityAmaintenanceDeterministic repository context packing for AI coding agents: selects, compresses, and budgets only the files a task needs. Measured 83% fewer input tokens at the same task coverage, fully local, no LLM in the loop.9100 PyPI9-
TDQS
Scored across 19 tools
Each tool targets a distinct functional area: context provision, navigation, analysis, documentation, custom rules, testing, and caching. Even similar tools like get_skeleton and get_ai_context have clearly differentiated purposes (skeleton-only vs. full context), eliminating ambiguity.
Tool names mix single-word domain identifiers (docs, compact, db, jsdoc, navigate, analyze, testing, filters) with snake_case verb phrases (get_focus_zone, invalidate_cache, set_custom_rule). While descriptive, the lack of a uniform verb_noun or noun_verb pattern across all tools makes naming slightly inconsistent.
The 19 tools are slightly above the ideal 3-15 range, but the server's broad scope (code graph navigation, analysis, documentation, testing, custom rules, AI context) justifies the count. Each tool serves a clear purpose, and no tool feels redundant.
The tool set provides comprehensive coverage of codebase analysis and AI assistance: navigation, quality analysis, test tracking, documentation management, custom rules, and context generation. Minor gaps like a missing delete_custom_rule are workable and do not create dead ends.