Scopewalker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOPEWALKER_ALLOWED_ROOTS | No | Comma-separated list of absolute paths that tools are allowed to operate on. Defaults to current working directory and system temp. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_line_countsB | Returns file line counts (code/blank/comment). Use extensions to filter. |
| get_functionsC | Returns function/method info. Use detail=lines for line counts per function. |
| check_thresholdsB | Finds files/functions exceeding size thresholds. Use limit to control output. |
| get_code_inventoryC | Lists classes, functions, methods, and exports. Use extensions to filter. |
| get_code_smellsB | Finds TODO/FIXME/HACK/BUG markers and unsafe casts in code. |
| get_complexity_metricsB | Returns complexity metrics (nesting, params, cognitive, per-function cyclomatic). Use limit/summary_only to control output. |
| get_documentation_coverageC | Finds undocumented functions/classes. Use limit/summary_only to control output. |
| get_prop_drillingB | Detects parameter threading (prop drilling) by finding parameter names passed through chains of functions. Use limit/summary_only to control output. |
| find_dead_codeA | Finds declared symbols that nothing references. dead_code is proven unreachable within the scan; unreferenced_exports may be used outside it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target a distinct analysis concern, but get_functions and get_code_inventory both enumerate functions/methods, and check_thresholds overlaps with get_line_counts and get_complexity_metrics since it operates on the same size/complexity data. Descriptions provide enough nuance to pick correctly in most cases, but the boundaries are not perfectly crisp.
Seven of nine tools follow a clean get_noun pattern, with only check_thresholds and find_dead_code deviating. The verb choice is semantically sensible (check for threshold comparison, find for searching), so the deviation is minor and readable rather than chaotic.
Nine tools is well-scoped for a code-analysis server, with each tool covering a distinct metric or scan type. No tool feels redundant padding or trivially thin.
The surface covers a broad set of static-analysis concerns: inventory, size, complexity, documentation, smells, dead code, and prop drilling. Minor gaps remain (e.g. cross-file dependency/import-cycle analysis or a raw symbol-reference lookup), but core codebase auditing workflows are well supported.