Skip to main content
Codex runs separately from the Monk extension. You keep Monk open in your IDE and launch Codex in the same project directory. This works for both the Codex CLI and the Codex IDE extension.
Coming soon: Headless mode — plug Monk directly into Codex without running a separate IDE window. Upvote it on our roadmap.

​
Setup

1

Enable Monk MCP

Open your project in VS Code, Cursor, Windsurf, or Antigravity with Monk installed. Run the command palette and choose Monk: Manage MCP Server → Enable MCP server. Pick Smart defaults or include Codex in the target list.Monk writes the config to .codex/config.toml in your project.Codex MCP Enablement
2

Open Codex in the same directory

Launch Codex CLI or open the project in the Codex IDE extension. Make sure the project is trusted by Codex so it reads the config.
3

Verify Monk is listed

Run /mcp inside Codex. Monk should appear in the active server list.
4

Start using Monk

Ask Codex to use Monk for deployment, infrastructure, or runtime tasks.

Deploy your first app

Monk is connected — now deploy your project

​
Troubleshooting

If Monk does not appear in /mcp, confirm the IDE with Monk is still running with the same project open and MCP is enabled. Make sure the project is trusted by Codex and that Codex is opened at the correct project root.

More troubleshooting

Common issues and how to fix them