mcp-architect
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ARCHITECT_ROOT | No | Optional: set to a fixed repository path so tools default to that root. |
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 |
|---|---|
| architecture_overviewA | High-level map of a codebase: languages, frameworks, size, structure, and entry points. Start here to understand an unfamiliar repo. Args: path: Repo path to analyze. Relative to the server's working directory (or MCP_ARCHITECT_ROOT if set). Defaults to the whole project. |
| dependency_graphA | Map how internal modules import each other, the most-depended-upon modules, and any circular dependencies. Use to understand coupling. Args: path: Repo path to analyze. language: 'auto', 'python', or 'js'/'ts'. |
| impact_analysisA | What could break if you change Args: target: Module or file to analyze, e.g. "app/core/db.py" or "app.core.db". If omitted, returns the highest-impact modules to pick from. path: Repo root. language: 'auto', 'python', or 'js'/'ts'. |
| hotspotsA | Find the files most worth attention: largest, most complex, most frequently changed (git), and highest combined risk. Args: path: Repo path to analyze. top: How many files per category (default 10). |
| explainA | Deep-dive a single folder or file: its files, public classes/functions, and external dependencies. Args: path: Repo root. module: Sub-path within the repo (folder or file) to explain. |
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 targets a distinct aspect of code analysis: high-level overview, dependency mapping, deep-dive explanation, complexity hotspots, and impact analysis. There is no overlap in purpose.
Four tools use descriptive noun phrases (architecture_overview, dependency_graph, hotspots, impact_analysis), but 'explain' is a single verb, breaking the pattern. The naming is still clear and mostly consistent.
Five tools cover the essential code analysis tasks without being excessive or insufficient. The set is well-scoped for a codebase exploration and refactoring server.
The tools cover the main analysis needs: high-level orientation, dependency understanding, detailed module explanation, risk identification, and change impact. No obvious gaps for the intended use cases.