wingbox
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WINGBOX_AUTO_REFRESH | No | Set to 0 to disable automatic graph refresh. While the graph misses known changes, MCP answers start with a stale-graph line instead of using it. | |
| WINGBOX_REFRESH_WAIT | No | The wait, in seconds, of MCP tools and query commands for a graph refresh (default 600 s). | 600 |
| WINGBOX_CHECK_INTERVAL | No | The interval, in seconds, that spaces out file-system checks for outside changes (default 0). | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Wingbox answers questions about the code graph of /app. Call impact before editing a file, analyze or quick to understand a module, boundary for the files to read. If a tool says the graph is missing, call build first; call build again after large edits.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buildA | Build or refresh the code graph of the repository (incremental; full=true reparses every file); call it first and after large edits. |
| impactA | Blast radius of changing a file: dependents by depth, counts, and the files to read first. |
| analyzeB | Full analysis of one module: entities, imports, dependents, key entities, layer and boundary files. |
| quickC | Find the module that best matches a keyword and analyze it in one step. |
| boundaryB | The files to read before changing a module: the module, what it imports and what imports it. |
| boundariesA | Check architecture layer violations (e.g. domain importing infrastructure) for one module or all. |
| layersA | List the modules grouped by architecture layer. |
| depsA | Outgoing dependency tree of a module: what it uses, hop by hop. |
| rdepsB | Reverse dependency tree of a module: who uses it, hop by hop. |
| entityB | Find where a class, function, type or constant is defined and every module that references it. |
| usagesA | Every place that uses one function, class, type or constant, through re-exports and aliases: by file, with line:column and the kind of use (import, re-export, call, type, extends, reference); method calls whose receiver type is not in sight are marked unresolved. |
| find_functionA | Find function and method definitions by name, with file and line. |
| find_typeB | Find class, interface, struct, enum and type definitions by name, with file and line. |
| find_callersB | Who calls a function: incoming calls, hop by hop. |
| find_callsB | What a function calls: outgoing calls, hop by hop. |
| find_callchainC | A call path from one function to another, or a module path when no call path exists. |
| diff_functionsB | Functions changed in the git diff against a ref (default HEAD), to check before review or commit. |
| queryA | Evaluate a Scheme query on the graph, e.g. (files (intersect (deps "A" 2) (rdeps "B" 1))). |
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 18 tools
Several tools overlap: entity, usages, find_function and find_type all locate definitions or references, while boundary vs boundaries and analyze vs quick are easy to confuse. Detailed descriptions help resolve most cases, but selecting the right tool still requires careful reading.
Most names are lowercase snake_case, but the conventions are mixed: find_* verb_noun tools sit alongside bare nouns (deps, impact, boundary, layers), verb-only names (query, build, analyze), and the near-identical boundary/boundaries. Readable, but not a predictable pattern.
18 tools is reasonable for a code-graph analysis server, and most cover distinct operations. A few, such as quick and entity, feel like convenience wrappers over other tools, so the set is slightly above the ideal 3-15 range.
The surface covers graph building/refresh, querying, dependency and reverse-dependency traversal, impact analysis, architecture layers and boundaries, call graph navigation, symbol lookup, usages, and diff inspection. There are no obvious lifecycle gaps for this domain.