Code Impact 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_impactA | Analyze the blast radius of changing specific files. Returns which files would be directly and transitively affected, with a risk score (0-1). Use BEFORE committing multi-file changes to understand what might break. Does NOT modify any files. |
| get_dependenciesA | Get the import and importedBy relationships for a specific file. Shows what this file depends on and what depends on it. Use to understand coupling before refactoring a file. |
| detect_cyclesA | Return strongly connected components with more than one file from the current dependency graph. Use it to inspect circular dependencies before refactors or release gates. |
| gate_checkA | Pre-commit safety gate. Analyzes specified changes and returns a PASS/WARN/BLOCK verdict with reasons. Use as a bounded decision aid before committing multi-file changes. BLOCK means current impact is too risky. WARN means human review recommended. PASS means low-risk. |
| refresh_graphA | Rebuild the dependency graph from scratch. Call this after significant file additions/deletions, or if analyze_impact results seem stale. Returns graph statistics including file count, edge count, build time, and any circular dependencies detected. |
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 5 tools
Each tool has a clearly distinct purpose: get_dependencies shows direct relationships, analyze_impact computes transitive blast radius, detect_cycles finds circular dependencies, gate_check provides a safety verdict, and refresh_graph rebuilds the graph. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (get_dependencies, analyze_impact, detect_cycles, gate_check, refresh_graph), making them predictable and easy to distinguish.
With 5 tools, the server is well-scoped for its purpose of dependency impact analysis. Each tool covers a necessary aspect, and there are no superfluous or missing tools for the core workflow.
The tool set covers the full lifecycle: graph building (refresh_graph), dependency inspection (get_dependencies), impact prediction (analyze_impact), cycle detection (detect_cycles), and pre-commit validation (gate_check). No obvious gaps for the intended use case.