CodeDoc MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_smart_docD | Universal tool for documentation and audits.
|
| scan_project_filesA | Returns a list of all documentable source files in the current project root. |
| refactor_and_optimizeC | Refactors and optimizes code. Handles case-insensitivity and deep path discovery. |
| evaluate_and_refactorC | Language-agnostic --- health audit AND generates optimized code. |
| predict_impactA | Analyzes the impact of changing a specific symbol (variable, function, or class). If no symbol is provided, it analyzes dependencies on the file itself. |
| global_security_auditA | Scans the ENTIRE project for secrets, keys, and vulnerabilities. Use this before pushing code to GitHub/GitLab. |
| guardian_scanA | Versatile security scanner.
|
| inspect_contract_changeA | Analyzes uncommitted changes to identify modified 'Contracts' (function signatures, class names, etc.) that require Sync. |
| heal_dependency_callsA | Finds and proposes updates for all files calling a modified symbol. Args: symbol_name: The name of the function or class that was modified. file_path: The source file where the change originated. change_type: e.g., 'RENAME', 'PARAM_ADDED', 'PARAM_REMOVED'. |
| apply_syncB | Generates and applies code patches to heal broken call-sites across the project. Args: symbol_name: The function/class name that was changed. change_type: 'RENAME', 'PARAM_ADDED', or 'STRUCT_CHANGE'. metadata: Dictionary containing 'new_name' or 'new_params'. |
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 10 tools
Multiple tools have overlapping purposes: refactor_and_optimize and evaluate_and_refactor both refactor/optimize code, while global_security_audit and guardian_scan both perform security scanning. generate_smart_doc is described as 'universal' and could be mistaken for an audit tool, adding confusion.
Naming conventions are mixed: some tools use verb_noun (scan_project_files, predict_impact), some use verb_and_verb (refactor_and_optimize, evaluate_and_refactor), and others use arbitrary adjectives (guardian_scan, generate_smart_doc). This inconsistency makes it harder to predict tool behavior from the name.
The count of 10 is within a reasonable range, but several tools serve nearly identical functions (two refactoring tools, two security scanners), suggesting the set is not well-scoped and redundant tools could be consolidated.
The server covers multiple areas (documentation, refactoring, security, impact analysis, dependency healing), but the name 'CodeDoc' suggests a focus on documentation, which is only represented by one broad tool. Missing features like updating existing documentation or verifying code post-refactor create notable gaps.