codex-mcp-dev

# Codex MCP Dev

Use the local Codex installation through the wrapper script at `{baseDir}/scripts/codex_mcp.py`.
This gives a stable path:

OpenClaw → mcporter → codex-mcp-server → local `codex`

## Quick Setup

Install prerequisites first:

- `mcporter`
- local `codex`
- `codex-mcp`

Create the project MCP entry if `config/mcporter.json` does not exist yet:

```bash
mcporter config add codex-cli --scope project --command codex-mcp
```

This skill expects a workspace-local MCP server named `codex-cli`.

## Workflow

1. Use this skill for non-trivial coding tasks.
2. If it is the first use in a session or something looks broken, run:
   - `python3 {baseDir}/scripts/codex_mcp.py doctor`
3. Choose a mode:
   - **Analysis / planning / explanation:** use `ask` without `--full-auto`
   - **Implementation / refactor / test-writing:** use `ask --full-auto`
4. Always set `--cwd` to the target repo or project directory.
5. Give Codex a concrete prompt with files, constraints, and acceptance criteria.
6. After Codex responds, inspect files and run local tests yourself when feasible instead of trusting the tool output blindly.
7. Summarize changes, tests run, and any remaining risks.

## Good Uses

- Implementing features across multiple files
- Fixing bugs with real repo context
- Refactoring with constraints
- Writing or updating tests
- Debugging failing commands or stack traces
- Asking local Codex for a second implementation pass or review

## Command Patterns

### Health check

```bash
python3 {baseDir}/scripts/codex_mcp.py doctor
```

### Version info

```bash
python3 {baseDir}/scripts/codex_mcp.py version
```

### Normal implementation

```bash
python3 {baseDir}/scripts/codex_mcp.py ask \
  --cwd /absolute/path/to/repo \
  --full-auto \
  --prompt "Implement the requested change, update tests, and summarize what changed."
```

### Read-only analysis

```bash
python3 {baseDir}/scripts/codex_mcp.py ask \
  --cwd /absolute/path/to/repo \
  --sandbox-mode read-only \
  --a...