Add the following to ~/.codex/config.toml. On Windows, the file is normally under %USERPROFILE%\.codex\config.toml.

[mcp_servers.odoo]
url = "https://your-odoo.example.com/mcp"
bearer_token_env_var = "ODOO_MCP_KEY"
enabled = true

Verify: run codex mcp list, start Codex, then use /mcp.

Create a project-level .mcp.json, or use the same server definition in your user configuration:

{
  "mcpServers": {
    "odoo": {
      "type": "http",
      "url": "https://your-odoo.example.com/mcp",
      "headers": {
        "Authorization": "Bearer ${ODOO_MCP_KEY}"
      }
    }
  }
}

Verify: run claude mcp list, start Claude Code, then use /mcp.

Open Settings → Tools & MCP and add a remote MCP server, or place a configuration file at .cursor/mcp.json for the project.

{
  "mcpServers": {
    "odoo": {
      "url": "https://your-odoo.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_KEY"
      }
    }
  }
}

Open Cline's MCP Servers page and add a remote Streamable HTTP server, or add the following entry to the Cline MCP configuration:

{
  "mcpServers": {
    "odoo": {
      "type": "streamableHttp",
      "url": "https://your-odoo.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_KEY"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Cline can use different model providers, including providers such as DeepSeek. MCP compatibility is supplied by the client, not by the selected language model.

Direct ChatGPT app or plugin integration requires a publicly reachable HTTPS MCP endpoint and a ChatGPT-compatible authentication flow. A static Bearer key alone may not be configurable in the ChatGPT user interface.