Codex

Prerequisites and availability

You need a Codex installation with remote MCP and OAuth support, and a Stratifyre account. Remote MCP plus portable skills is the supported baseline. Native Codex packaging is optional and is available only when the published compatibility information records a passing pinned smoke test.

Release/evidence pin: @stratifyre/[email protected], Codex CLI 0.152.0 fixture, fallback path only; client smoke evidence not recorded.

Connect and verify

Add and authorize the production server:

codex mcp add stratifyre --url https://app.stratifyre.com/mcp
codex mcp login stratifyre
codex mcp list

Complete OAuth in the browser opened by Codex. Confirm the server appears in the list; use only Codex-managed configuration and do not commit OAuth material.

For first use, ask Codex to discover the live manifest, inspect available status and scopes, and read existing strategies. Explicitly prohibit creates, updates, deletion, and backtests for this first task.

Create, backtest, and limits

After verification, ask Codex to prepare complete strategy_workspace_create and strategy_refine_nl payloads and show them for approval. Create the unsaved workspace once, submit its message, and poll strategy_workspace_get until a reviewed outcome is available. Resolve clarification or review the proposal, explicitly save the selected revision with strategy_workspace_save, then call strategy_get. For a backtest, review and approve the complete backtest_start payload, poll backtest_status, and inspect the result. Resolve named instruments in Stratifyre or provide canonical IDs; the current MCP manifest has no direct market-data search tool. Capabilities and limits come from the live server, OAuth scopes, entitlements, job limits, and your Codex workspace.

Approval in the conversation is agent guidance, not server enforcement. Independent candidates can partially fail; do not imply batch atomicity or retry without review.

Update, remove, or use the portable fallback

Update with the next versioned fallback bundle and replace both skill directories together. Remove the stratifyre entry with codex mcp remove stratifyre, delete copied skills, and revoke the OAuth authorization in Stratifyre if desired. Native Codex packaging is not published because its pinned smoke test is not run.

Documentation basis: OpenAI Codex MCP documentation, https://developers.openai.com/codex/mcp/, checked 2026-09-01; the named client fixture is not yet smoke-tested.

Next steps

Continue with Work with Stratifyre for strategy and backtest workflows. See Troubleshooting and Security for portable skills, permission limits, interrupted jobs, updates, and removal.