ctx-gen-mcp
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 |
|---|---|
| scan_skeletonA | Scan a code repository and return a deterministic module skeleton. Args: project_dir: Absolute path to the project root directory. depth: Directory depth for auto-detecting modules (default 2). code_only: If True, only include code files (default True). Returns: A dict with: root_path, total_modules, total_files, total_lines, modules[]. |
| validate_coverageA | Validate that every module has a generated context JSON, and detect stale ones. Args: project_dir: Path to the project root. ctx_dir: Path to the ctx/ output directory. check_stale: If True, detect modules whose source has changed (default True). Returns: Dict with: total_modules, generated, coverage_pct, missing_ids[], stale_ids[], unknown_fields_summary{}. |
| assemble_docsC | Assemble all per-module JSON context files into progressive-disclosure MD docs. Args: project_dir: Path to the project root. ctx_dir: Path to the ctx/ directory with per-module JSONs. out_docs: Output directory for MD docs. project_name: Optional project name (default: inferred from project_dir). Returns: Dict with: main_doc, module_docs[], errors[]. |
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 3 tools
Each tool targets a distinct phase in the documentation generation workflow—scanning, assembling, and validating—with no functional overlap.
All tool names follow a consistent verb_noun pattern (assemble_docs, scan_skeleton, validate_coverage) with clear action and object.
Three tools are well-scoped for a context generation server, covering the essential operations without excess or deficiency.
The tool surface covers the core workflow (scan, assemble, validate), but lacks a tool to manage or regenerate specific context files manually.