codex-cli-architect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_MODEL | No | Model to use (default: gpt-5) | gpt-5 |
| CODEX_TIMEOUT | No | Execution timeout in milliseconds (default: 300000) | 300000 |
| OPENAI_API_KEY | No | OpenAI API key for authentication (optional, uses ChatGPT login if not provided) |
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 |
|---|---|
| codex_consultB | Technical consultation for architecture decisions, design patterns, technology choices, and implementation strategies |
| codex_reviewA | Review code for a feature, component, or Git changes. Codex analyzes the relevant implementation or modified files, providing contextual feedback and improvement suggestions |
| codex_explainA | Explain code, features, or changes. Codex examines the implementation, Git history, or conceptual design to provide comprehensive explanations |
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
The three tools are largely distinct: consult is clearly separate, while explain and review both analyze code but differ in intent (understanding vs. critique). This boundary is clear enough for most cases, though explain and review could still be confused in edge scenarios.
All tool names follow the same predictable pattern: codex_ prefix plus a lowercase imperative verb in snake_case. The naming is consistent and each verb clearly reflects the tool's purpose.
Three tools is at the low end of the typical range, but each covers a distinct architect-focused activity: explain, consult, and review. The count is reasonable for a narrow assistant, though a broader architecture server could justify more tools.
The toolset covers core advisor-style workflows: understanding code, getting technical guidance, and reviewing changes. It lacks generative or planning tools, but that appears acceptable for an architect/consultant role rather than an active coding agent.