Control-PromotionMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind the HTTP server (only for http mode). | 127.0.0.1 |
| MODE | No | Transport mode: stdio or http. | stdio |
| PORT | No | Port to bind the HTTP server (only for http mode). | 8765 |
| ADAPTER | Yes | Path to the project adapter YAML file. | |
| PROJECT_ROOT | Yes | Path to the project root directory. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_projectC | Inspect repository structure and detected governance controls. |
| evaluate_control_candidateB | Evaluate a proposed rule, guard, skill, or remediation and decide its control maturity. |
| route_control_destinationC | Route a failure class to docs, Skill, quality guard, QA harness, or contract prevention. |
| validate_smell_catalogB | Validate a smell catalog file for required control-promotion fields. |
| validate_project_adapterC | Validate a project adapter file. |
| render_smell_gate_reportC | Render a Markdown smell gate report from a candidate or review object. |
| check_ssot_linksC | Classify symlinked SSOT paths and recommend safe edit routing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review-control-candidate | Review a proposed rule, guard, skill, or remediation and decide its control level. |
| promote-experience | Turn an incident, repeated fix, or experience into a control asset decision. |
| retire-guard | Assess whether an old guard can be retired after stronger prevention exists. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Control maturity ladder | |
| control://routing-matrix | |
| control://smell-rubric | |
| control://proof-obligations | |
| control://retirement-policy | |
| catalog://base | |
| template://smell-gate-report | |
| Project adapter | |
| Project smell catalog |
TDQS
Scored across 7 tools
Each tool targets a distinct operation: checking symlinked paths, evaluating control candidates, inspecting projects, rendering reports, routing failure classes, and validating two different file types. No overlap in purposes.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., check_ssot_links, evaluate_control_candidate). The naming convention is uniform across the set.
7 tools is appropriate for a specialized domain like control promotion. It is neither too few to be trivial nor too many to be overwhelming.
The tools cover the core workflow of checking, evaluating, inspecting, rendering, routing, and validating. A minor gap is the lack of explicit creation or update operations for control candidates, but the set is largely complete for its stated purpose.