Connect
Connect MiraDock to Codex CLI
Codex CLI connects to MiraDock with a Bearer token.
Before you start
- You need a MiraDock account. Sign up at /auth/sign-up.
- Generate a write token at /app/mcp.
Configuration
[mcp_servers.miradock]
url = "https://miradock.com/mcp"
http_headers = { Authorization = "Bearer <YOUR_TOKEN_HERE>" }- `[mcp_servers.miradock]` registers MiraDock as a named Codex MCP server.
- `url` points Codex CLI at MiraDock's MCP endpoint.
- `http_headers.Authorization` sends your write token with each MCP request.
Setup walkthrough
- Generate a MiraDock write token from the Your tokens section in /app/mcp.
- Copy the token immediately; it is only shown once.
- Add the TOML above to ~/.codex/config.toml, or run: export MIRADOCK_MCP_TOKEN="<YOUR_TOKEN_HERE>"; codex mcp add miradock --url "https://miradock.com/mcp" --bearer-token-env-var MIRADOCK_MCP_TOKEN
- Replace <YOUR_TOKEN_HERE> with the full secret, then restart Codex CLI or run /mcp in the TUI.
- Verify the connection with the prompt below.
What success looks like
Codex CLI should show MiraDock in its MCP server list and allow the agent to call MiraDock tools.
Read the MiraDock Game SDK and help me build, validate, and publish a small Game.Common errors
Error: Connection refused.
Fix: Check your CLI version supports MCP, then restart Codex CLI after editing the config file.
Error: Token rejected.
Fix: Confirm the header value is 'Bearer <token>' and that the token has not been revoked.
Error: Config changes are ignored.
Fix: Restart Codex CLI or run /mcp in the TUI after saving ~/.codex/config.toml.