WLADY_CODE MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WLADY_UI_PORT | No | Change UI port (default: 9750). Set to '0' to disable the UI entirely. | 9750 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_repositoryA | Index a code repository to build the symbol graph. Supports incremental updates. |
| list_projectsB | List all indexed projects with their stats. |
| delete_projectB | Remove a project and all its indexed data from the database. |
| contextA | Get the context around a symbol: its definition, callers, callees, and file siblings. |
| whereC | Find where a symbol is defined. |
| pathC | Find the shortest call path between two symbols. |
| trace_pathB | Trace all call paths from a symbol (upstream callers or downstream callees). |
| briefA | Get a brief overview of a file: its symbols, imports, and exports. |
| mapB | Get a structural map of the project: top files by connectivity, module clusters. |
| search_codeA | Search source code text across all files in the project (grep-like). |
| search_graphA | Search over the symbol graph. BM25 by default; pass semantic:true for hybrid BM25+vector search (requires embeddings to be generated during index_repository). |
| query_graphC | Run a raw SQL-like structured query against the symbol graph. |
| fn_impactB | Analyze the impact of changing a function: find all upstream callers affected. |
| diff_impactC | Analyze the impact of current git changes: which symbols are affected and who calls them. |
| detect_changesB | Detect which files have changed since last index (using mtime/hash comparison). |
| branch_compareC | Compare symbols between two git branches to see what changed. |
| auditB | Audit the codebase for quality issues: dead code, high complexity, missing coverage, circular deps. |
| rolesB | Classify and display the roles of symbols in the project (entry, core, utility, adapter, dead, leaf). |
| complexityB | Show complexity metrics for symbols in the project, sorted by complexity. |
| communitiesC | Detect code communities/clusters using graph connectivity analysis. |
| get_architectureB | Get a high-level architecture overview: layers, modules, dependency graph summary. |
| manifestoC | Manage project quality manifesto rules (thresholds for complexity, dead code, etc.). |
| checkB | Run manifesto checks against the current codebase state. Returns PASS/WARN/FAIL per rule. |
| adr_listC | List Architecture Decision Records (ADRs) for the project. |
| adr_createC | Create a new Architecture Decision Record. |
| adr_updateB | Update an existing Architecture Decision Record. |
| execution_flowA | Trace the execution flow from an entry point (or auto-detect entry points). Shows the call tree depth-first with cycle detection. |
| list_entry_pointsA | Detect and list likely entry points in a project (main, handlers, HTTP routes, etc.). |
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 28 tools
Most tools are clearly distinct, but some overlap exists between trace_path and execution_flow, and between audit, check, and manifesto. Overall, the boundaries are well-defined.
Naming is mostly lower_case with underscores, but patterns vary (verb_noun, noun_verb, single verb). Consistency is moderate; not chaotic but not uniform.
28 tools is high but justified by the broad code analysis domain. It slightly exceeds the ideal range, but each tool serves a distinct purpose.
The tool set covers indexing, searching, architecture, impact analysis, quality checks, ADR management, and more. No obvious gaps for the stated purpose.