Connect Codex to Builder MCP v2
Register the Flowgear Builder MCP endpoint in Codex, complete OAuth, verify the target context, and load Builder Guidance before allowing Workflow changes.
Register the server
The quickest path is to copy the Setup with your Coding Agent prompt from the Builder MCP section of the Console's MCP page and paste it into Codex. The prompt already contains the Server URL and the recommended server name. To register the server manually instead:
-
Open
MCPfrom the Console's main navigation. In theBuilder MCPsection, copy theServer URLandRecommended name. -
Verify the Server URL,
https://<environment-hostname>/mcp/builder, in a browser. -
Run the following, replacing
<recommended-name>with the recommended name you copied:codex mcp add <recommended-name> --url https://<environment-hostname>/mcp/builder -
If OAuth does not start automatically, run:
codex mcp login <recommended-name> -
Complete Flowgear sign-in in the browser.
The recommended name keeps this server distinguishable from other Flowgear MCP servers you have configured. You can choose a different name, but use the same name in both commands. Codex can keep several Flowgear MCP servers configured at once, such as one for each Tenant and Site you work with.
Verify the connection
Run codex mcp list to check the configured server, or open /mcp in the Codex terminal UI. Then ask Codex to use that server to:
- Read
flowgear://builder/guidanceonce. - Call
GetBuilderContext. - Show the connected Tenant, Site, and Environment without making changes.
Stop if the returned context is not the intended Test Environment. Do not also call GetBuilderGuidance when the Resource was loaded successfully.
Set approval expectations
Builder MCP includes read and write Tools. Keep approval prompts appropriate to the risk, especially for SaveWorkflow, DebugWorkflow, folder creation, or a test that can mutate an external system. Review Codex MCP approval settings before a long build session.
Start with Build a Workflow with Builder MCP. Current Codex MCP registration and OAuth commands are documented in the official OpenAI MCP documentation.