GDScript Code Analyzer
Related Servers
Alternatives to GDScript Code Analyzer
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceAnalyzes source code structure across multiple languages using tree-sitter, extracting classes, functions, methods, and metadata with precise line numbers for efficient codebase exploration and AI-assisted development.13697 PyPI3MIT
- 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 gradedqualityDmaintenanceEnables precise code extraction from 30+ languages using tree-sitter parsing, allowing AI assistants to retrieve functions, classes, and code snippets with accurate line numbers.8MIT
- AlicenseAqualityDmaintenanceProvides code context and analysis for AI assistants by extracting directory structures and code symbols using WebAssembly Tree-sitter parsers with zero native dependencies.112 npm20MIT
- 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
- AlicenseNot gradedqualityBmaintenanceProvides 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.11 npm1MIT
TDQS
Scored across 8 tools
The tools have overlapping purposes that could cause confusion, such as analyze_gdscript_code vs. analyze_gdscript_file vs. get_gdscript_structure, which all seem to extract code structure but with subtle differences in input or output. However, descriptions help clarify some distinctions, like find_gdscript_symbol being for specific symbols versus find_references for broader usage tracking.
All tool names follow a consistent snake_case pattern with clear verb_noun combinations (e.g., analyze_gdscript_code, find_gdscript_symbol, get_gdscript_dependencies). There are no deviations in naming style, making the set predictable and easy to parse.
With 8 tools, the count is well-scoped for a GDScript code analyzer, covering analysis, searching, dependency tracking, and project management. Each tool appears to serve a distinct role without unnecessary bloat, fitting typical expectations for this domain.
The tool set provides strong coverage for static analysis tasks in GDScript, including code structure extraction, symbol lookup, reference tracking, and project setup. A minor gap exists in dynamic or runtime analysis capabilities, but core workflows for code understanding are well-supported.