Skip to main content
Glama
git-project-xray-mcp

git-project-xray-mcp

Related Servers

Alternatives to git-project-xray-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      4
      52
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      4
      489
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      18 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to perform fast regex/text and structural AST searches across codebases, find symbols, list files, and safely preview or apply refactors. It unifies ripgrep and ast-grep with pagination, gitignore-aware defaults, and fallback engines for zero-setup code search.
      6
      18 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to explore a repository by querying a pre-built structural knowledge graph of symbols and their relationships — definitions, callers, callees, blast radius, and file-level impact — instead of grepping and reading files. This cuts the tokens spent on code exploration by roughly 96–99% while running entirely on local SQLite with tree-sitter parsing.
      1
      MIT

    TDQS

    A4.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing