superpower-codex-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPERPOWER_ANTIGRAVITY_COMMAND | No | Path to the Antigravity CLI executable if not in default location. Defaults to %LOCALAPPDATA%\agy\bin\agy.exe on Windows or agy in PATH on other platforms. | |
| SUPERPOWER_CODEX_ALLOWED_ROOTS | No | Semicolon-separated (Windows) or colon-separated (macOS/Linux) list of allowed workspace roots. Defaults to the MCP process working 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_workspaceA | Validate and canonicalize a workspace before loading context or starting Gemini. Returns structured authorization and capability diagnostics without modifying files or invoking a model. |
| summarize_repo_contextA | Read repository instruction files such as AGENTS.md and GEMINI.md. Returns startup context for Gemini CLI before coding. |
| plan_with_codexA | Ask Codex to create a Superpowers-style implementation plan before Gemini CLI edits code. Returns and saves the plan. |
| review_with_codexA | Ask Codex to review the current diff or selected files. Returns findings first, ordered by severity. |
| debug_with_codexA | Ask Codex to analyze a failure using systematic debugging without applying fixes. |
| verify_with_codexB | Gate completion claims. Plans verification or runs explicitly allowed commands and asks Codex to assess the evidence. |
| run_development_workflowA | Orchestrate plan, implement, review, fix, and verify stages. Codex plans, reviews, and verifies; Antigravity executes coding and fix iterations. |
| review_code_qualityA | Static analysis pre-filter for Codex. Scans TypeScript files for |
| run_gemini_coding_taskC | Deprecated compatibility alias for run_antigravity_coding_task. Invokes Antigravity CLI for coding. Supports strict execute/plan contracts, Git-verified commits and file scope, acceptance-test traceability, and compact responses with persisted diagnostics. |
| run_antigravity_coding_taskC | Canonical coding execution tool. Invokes Antigravity CLI while Codex retains planning, review, debugging, and verification responsibilities. Supports strict execute/plan contracts, Git-verified commits and file scope, acceptance-test traceability, and compact responses with persisted diagnostics. |
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 10 tools
Most tools have clear, distinct responsibilities: planning, review, debugging, verification, static analysis, and coding execution are separated cleanly. The only real ambiguity comes from run_gemini_coding_task being a deprecated alias of run_antigravity_coding_task, though this is explicitly documented.
All tool names follow a consistent lowercase snake_case verb_phrase pattern, and the repeated with_codex suffix signals which actions invoke Codex. The naming is predictable and scannable, with no mixed casing or irregular verb styles.
Ten tools is well within the appropriate range for a workflow-oriented MCP server. Each tool maps to a distinct workflow stage or support function, and the deprecated compatibility alias is not enough to make the set feel bloated.
The tool surface covers the full development loop: workspace validation, context loading, planning, static analysis, LLM review, debugging, verification, and coding execution. The orchestration tool additionally ties these stages together, so there are no significant dead ends or missing lifecycle operations.