Connect Codex to Docker Engine
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 Docker Engine
A preset of real Docker Engine operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Docker Engine
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
Docker Engine
12 toolsIdentify the connected Docker Engine and summarize its inventory.
Read the Docker Engine version and supported API versions.
List containers and their status.
Read a container's image, status, and creation time.
Start an existing stopped container.
Stop an existing running container.
Restart an existing container.
Pause processes in an existing container.
Resume processes in an existing paused container.
List local images with their tags and sizes.
List available Docker networks and drivers.
List Docker volumes and their drivers.
About Codex
Frequently asked questions
More ways to connect
More tools for Codex
Use Docker Engine with other agents
Open your Codex agent in one click.
NoClick runs Codex for you with Docker Engine wired in as tools. Connect your account and run.