tree-sitter-analyzer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TREE_SITTER_OUTPUT_PATH | No | Optional path for large output write target. | |
| TREE_SITTER_PROJECT_ROOT | Yes | Absolute path to the project root directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Code-intelligence (codegraph-compatible) search facade. Actions: chain, query, select, semantic, subscribe, symbol, text, tql_execute, tql_schema, unsubscribe. Pass action=help with target_action for an exact action schema. |
| navA | Code-intelligence (codegraph-compatible) navigation facade. Actions: call_path, callee_tree, callees, caller_tree, callers, co_change, context, impact, lineage, navigate, pulse, pulse_batch, resolve, test_map, trace, xref. Pass action=help with target_action for an exact action schema. Cost: action=callers is slow (prefer nav action=context (1-hop, warm)). |
| structureB | Code-intelligence (codegraph-compatible) structural analysis facade. Actions: analyze, ast_path, class_detail, class_tree, explore, outline, read, signatures, sitemap. Pass action=help with target_action for an exact action schema. |
| healthA | Code-intelligence (codegraph-compatible) health and analysis facade. Actions: dead, deps, file, heatmap, imports, matrix, middleware, overview, patterns, project, refactor_queue, routes, scale, self, test_gap, unreachable. Pass action=help with target_action for an exact action schema. Cost: action=project is slow (prefer health action=file (one file, warm)). |
| editB | Code-intelligence (codegraph-compatible) safety and change-management facade. Actions: ast_diff, classify, constraints, guard, impact, mutation_probe, plan_rename, pr, refactor, release_snapshot, rename, safe, verify. Pass action=help with target_action for an exact action schema. Cost: action=safe is slow. |
| projectC | Code-intelligence (codegraph-compatible) project-intelligence hub. Actions: card, doc_sync, journal, metrics, overview, parser, skills, smart, workflow. Pass action=help with target_action for an exact action schema. |
| indexB | Code-intelligence (codegraph-compatible) index lifecycle hub. Actions: auto, build, cache, full, knowledge, schema, status, sync. Pass action=help with target_action for an exact action schema. |
| vizB | Code-intelligence (codegraph-compatible) visualization and similarity facade. Actions: graph, knowledge, similarity, uml. Pass action=help with target_action for an exact action schema. |
| set_project_pathA | SMART Workflow 'Set' step (FIRST): Set the project root path for security boundaries. Call this before any other tool to ensure correct file resolution and security validation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| smart_analyze | SMART Workflow: Systematic code analysis for a single file. Recommended for files you haven't seen before. |
| smart_explore | SMART Workflow: Explore a new project. Get the full picture before diving into code. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| code_file | Access to code file content through URI-based identification |
| project_stats | Access to project statistics and analysis data |
| Hyphae selector result | Re-evaluate a Hyphae selector expression and return the current result set. URI produced by search action=subscribe. |
TDQS
Scored across 9 tools
The facades have broadly overlapping exploration duties: search, nav, and structure all feel like code-navigation surfaces, and shared action names such as impact, overview, and knowledge appear in multiple tools. An agent would struggle to pick a tool without first querying action=help, since the boundary between facades is not clear from the names or action lists alone.
The eight codegraph facades follow a consistent lowercase single-word naming style (search, nav, structure, health, edit, project, index, viz), which is predictable across the set. The exceptions are the verb-noun set_project_path and the abbreviations nav/viz, which are minor deviations rather than a chaotic mix.
Nine tools is a well-scoped count for a code-intelligence suite: setup, indexing, searching, navigation, structural analysis, health, editing, project intelligence, and visualization each have a dedicated facade. Each tool bundles many actions but remains a single cohesive entry point, so the count feels intentional rather than excessive or thin.
The surface covers the full expected lifecycle for a code analyzer: project initialization, index management, code search, navigation, AST/structural analysis, health analysis, safe refactoring/editing, project metrics, and visualization. The edit facade even includes verification and mutation-probe actions, and health/test-gap covers quality checking, leaving no obvious dead end or missing major capability.