Summer Engine in Codex
Codex is OpenAI’s AI coding assistant that supports MCP (Model Context Protocol). With Summer Engine’s integration, Codex can control your game engine: add nodes to scenes, set properties, import assets, run the game, and debug, all from within your coding workflow. This guide covers the configuration. Setup takes about a minute.Prerequisites
- Codex: OpenAI’s AI coding assistant (CLI or IDE extension)
- Node.js 22+: For running the MCP server
- Summer Engine: Open with your project, for engine work only
- Sign in once:
npx -y summer-engine@latest login. One browser sign-in also connects the store, publishing and Grow tools
Configuration
Codex uses TOML configuration. The config file is:- User-level:
~/.codex/config.toml(applies to all projects) - Project-level:
.codex/config.tomlin your project root (trusted projects only)
Option 1: CLI (Recommended)
Add Summer Engine with a single command:Option 2: Edit config.toml
Create or edit~/.codex/config.toml and add:
Step 3: Restart Codex
Close and reopen Codex (or the IDE extension) so it loads the new MCP config. The Summer Engine MCP server starts when Codex starts; it connects to the engine on the first tool call.Step 4: Verify
In the Codex TUI, use/mcp to see your active MCP servers. You should see “summer-engine” listed, with its tools available. Then try a prompt:
- “Use Summer Engine to add a MeshInstance3D with a BoxMesh to the scene”
Cloud work only: connect by URL
For assets, plans, the store, publishing and Grow, with nothing to install, add the hosted Summer server. The second command opens your browser to sign in:summer login, the local server also runs the cloud tools, so use one of the two.
Using Summer Engine with Codex
Once configured, Codex can use Summer Engine’s tools when you ask for game-related changes. Example prompts:- “Add a Camera3D and DirectionalLight3D to the scene root”
- “Get the scene tree from Summer Engine”
- “Import this model and add it to the World node: [URL]”
- “Run the game and capture a screenshot”
- “Set the project’s main scene to res://main.tscn”
Troubleshooting
”Summer Engine is not running” (engine_not_running)
Start Summer Engine and open your project. The MCP server connects to the engine’s local API on port 6550. The engine writes a token to ~/.summer/api-token when it starts.
Every Summer error names its code and one next step (next). not_signed_in: run npx -y summer-engine@latest login. no_credits: add credits at https://www.summerengine.com/studio/credits. All codes: How Summer answers.
MCP server not appearing
- Config path: Verify
~/.codex/config.tomlexists (or.codex/config.tomlfor project scope) - TOML syntax: Ensure valid TOML (no trailing commas, proper section headers)
- Restart: Fully quit and reopen Codex
Tools return errors
See Value formats for parameter formats. Common issues: wrong node path format (./World/Player), invalid property values (use engine string format like "Vector3(0, 10, 0)"), or the game running when scene edits are attempted (stop it first with summer_stop).
Next Steps
Operations reference
Every operation with its inputs and an example
Building a Game
How an AI builds a full game using MCP
MCP Setup Overview
Architecture, prerequisites, and other IDEs
CLI Reference
summer install, run, create, and more
Need help? Ask in Discord first. That is where you get the fastest reply and support. For concrete help, email support@summerengine.com or founders@summerengine.com.

