git-project-xray-mcp
Related Servers
Alternatives to git-project-xray-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to understand and navigate codebases through structural analysis. Provides code mapping, symbol search, and impact analysis using ast-grep for accurate parsing of Python, JavaScript, TypeScript, and Go projects.452MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search and analyze codebases using Abstract Syntax Tree (AST) pattern matching with ast-grep. Supports structural code search, pattern testing, and AST visualization across multiple programming languages.4466MIT
- AlicenseNot gradedqualityCmaintenanceProvides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.9 npm1MIT
- FlicenseNot gradedqualityAmaintenanceProvides efficient code navigation and graph-based analysis for AI agents, enabling symbol resolution, callers, implementations, and type schemas with minimal token usage.-
- FlicenseAqualityCmaintenanceEnables token-efficient structural code exploration using tree-sitter AST parsing, with tools for symbol search, outlines, source unfolding, call graphs, and related-file discovery.1-
- AlicenseNot gradedqualityAmaintenanceExposes a codebase's symbol graph and symbol-aware editing tools to AI agents, enabling targeted symbol lookup, impact analysis, and atomic multi-file edits with reduced context tokens.12 npmMIT
TDQS
Scored across 3 tools
Each tool has a distinct, non-overlapping purpose: explore_repo for directory structure, find_symbol for locating code symbols, and what_breaks for impact analysis. The workflow is clearly sequenced, so an agent can easily select the right tool for each step.
All tool names follow a consistent verb_noun pattern (explore_repo, find_symbol, what_breaks). The names are descriptive and align with their functions, with 'what_breaks' being a slight phrase but still fitting the pattern.
With only 3 tools, the server is tightly scoped to a progressive discovery workflow. Each tool earns its place, and the count is ideal for the focused purpose of code exploration and impact analysis.
The tools cover the core workflow of exploring structure, finding symbols, and checking references. Missing features like direct file content reading or diff analysis are minor given the stated use case, but they are not critical gaps.