codex-mcp-agent
Note: This project is a fork of the current Git remote:
Enable Claude Code, Cursor and other AI tools to call Codex for task execution. Plus/Pro/Team subscribers can maximize GPT-5 usage without additional costs.
Setup
1. Install Codex CLI
npm install -g @openai/codex
codex login
2. Configure MCP
Add to your .mcp.json:
Safe Mode (Default):
{
"mcpServers": {
"codex": {
"type": "stdio",
"command": "uvx",
"args": ["codex-mcp-agent@latest"]
}
}
}
Writable Mode:
{
"mcpServers": {
"codex": {
"type": "stdio",
"command": "uvx",
"args": ["codex-mcp-agent@latest", "--yolo"]
}
}
}
Or use Claude Code commands:
# Safe mode (default)
claude mcp add codex-mcp-agent -- uvx codex-mcp-agent@latest
# Writable mode
claude mcp add codex-mcp-agent -- uvx codex-mcp-agent@latest --yolo
Tools
The MCP server exposes two tools:
codex_execute(prompt, work_dir)- General purpose codex executioncodex_review(review_type, work_dir, target?, prompt?)- Specialized code review
If you have any other use case requirements, feel free to open issue.
HTTP/SSE Mode (Optional)
For local personal use, you can run the server over HTTP with Server-Sent Events (SSE) and connect via type: "sse".
Start the server in SSE mode:
uvx codex-mcp-agent@latest --sse # safe mode, localhost:8822
uvx codex-mcp-agent@latest --sse --yolo # writable mode
# Options
# --host (default: 127.0.0.1)
# --port (default: 8822)
Configure your client .mcp.json:
{
"mcpServers": {
"codex": {
"type": "sse",
"url": "http://127.0.0.1:8822"
}
}
}
Notes:
- SSE mode keeps the same Safe/Writable behavior controlled by
--yolo. - SSE server binds to
127.0.0.1by default and has no auth/CORS for simplicity. - Stdio mode remains the default; use
--sseonly if you prefer HTTP.
Optional: Streamable HTTP transport (if your client supports it):
uvx codex-mcp-agent@latest --http # safe mode streamable-http transport
Safety
- Safe Mode: Default read-only operations protect your environment
- Writable Mode: Use
--yoloflag when you need full codex capabilities - Sequential Execution: Prevents conflicts from parallel agent operations
Metadata
Release files for codex-mcp-agent 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| codex_mcp_agent-0.1.0.tar.gz | 51.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codex_mcp_agent-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.1 kB
Release files / codex_mcp_agent-0.1.0.tar.gz
| Download URL | codex_mcp_agent-0.1.0.tar.gz |
|---|---|
| Size | 51.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5c514c65a622fb3de3751c3c271cbc9a4dee1c8b199362e7546098992f22683
|
|
BLAKE2b-256 checksum How to use checksums |
e44b262c04331abcc63901a80e4cfaf41dcf6d1fd029e79649725353b9dbd3f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / codex_mcp_agent-0.1.0-py3-none-any.whl
| Download URL | codex_mcp_agent-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96013faea383a084fe7a25ad272583df8297b946573483fee5652a3cef58ea52
|
|
BLAKE2b-256 checksum How to use checksums |
8f75f8aea1e40179c7bc673bb1fb27dd6efc44fa2bae4a90767eafbd312b125d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for codex-mcp-agent 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.