Connect Codex and other MCP clients

Configure a local MCP client with Doodi’s server URL and the token you created in Account settings.

Copy the Codex configuration

In the connection setup, choose Codex → Copy configuration. Add it to your Codex config.toml, then restart the client. Use the URL displayed by your Doodi instance.

The following example intentionally contains a placeholder:

[mcp_servers.doodi]
url = "http://127.0.0.1:17481/mcp"
http_headers = { Authorization = "Bearer <your Doodi token>" }
tool_timeout_sec = 180

Keep a configuration containing a real token private. Replace a lost token by revoking the connection and creating a new one.

Use an environment variable

If you manage the client’s launch environment, store the token in DOODI_MCP_TOKEN and reference it:

[mcp_servers.doodi]
url = "http://127.0.0.1:17481/mcp"
bearer_token_env_var = "DOODI_MCP_TOKEN"
tool_timeout_sec = 180

A desktop app opened from Finder does not inherit a variable exported in an unrelated terminal. Use the configuration-header method or set the environment of the actual client process. Restart after changing its configuration or launch environment.

Codex’s supported HTTP authentication fields are documented in the official MCP guide .

Other clients

Choose Streamable HTTP, supply the displayed URL, and send Authorization: Bearer <token>. A common configuration shape is:

{
  "mcpServers": {
    "doodi": {
      "url": "http://127.0.0.1:17481/mcp",
      "headers": {"Authorization": "Bearer <your Doodi token>"}
    }
  }
}

Each client defines its own configuration format. Use its HTTP MCP settings rather than assuming this JSON is universal.

Confirm the connection

Ask: “List my Doodi projects and read the brand facts for the project I select. Do not change anything.”

If tools are missing, check permissions, expiry, the endpoint, the signed-in Doodi account and whether the client was restarted. See permissions and troubleshooting.