Connect Codex to Dev Cycle
Set up in minutes
Choose where it runs
On your computer through your own Codex, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in Dev Cycle
A preset of real Dev Cycle operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Dev Cycle
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your Codex first calls in. Codex connects when a session starts — run codex, or restart a running one (in the Codex app, Restart).
Run this in your terminal. The Codex app shares its config, so it gets the server too
<your-link> is your personal server URL — setup mints it for you.
Tools Codex gets
Dev Cycle
25 toolsPermanently delete the project and its resources.
Permanently delete this environment.
Create a feature with explicit environment states and no targeting rules.
Update feature metadata without changing targeting rules.
Change lifecycle status; complete serves the specified static variation.
Update static variable values and environment states.
Permanently delete this variable.
About Codex
Frequently asked questions
More ways to connect
More tools for Codex
Use Dev Cycle with other agents
Open your Codex agent in one click.
NoClick runs Codex for you with Dev Cycle wired in as tools. Connect your account and run.