# Codex CLI

> Part of the OVHcloud developer hub. Index of every page and section: https://developers.eu.ovhcloud.com/llms.txt
> Everything in one file: https://developers.eu.ovhcloud.com/llms-full.txt

Set up the OVHcloud MCP server in Codex CLI.

Preview: the OVHcloud MCP server is to be confirmed

Nothing answers at `https://mcp.eu.ovhcloud.com/mcp` yet. Its URL and its tools are this page's proposal, the way the guides below will read once it does.

## Prerequisites

- Codex CLI installed
- Node.js 22+ installed
- An OVHcloud API token (see [Authentication](https://developers.eu.ovhcloud.com/authentication.md))

## Configuration

1. Open ~/.codex/config.toml, or create it.
2. Add the OVHcloud server, and replace YOUR_OVHCLOUD_TOKEN with your token:
  ```toml
  [mcp_servers.ovhcloud]
command = "npx"
args = [
  "-y",
  "mcp-remote@latest",
  "https://mcp.eu.ovhcloud.com/mcp",
  "--header",
  "Authorization:${OVH_AUTH_HEADER}"
]

[mcp_servers.ovhcloud.env]
OVH_AUTH_HEADER = "Bearer YOUR_OVHCLOUD_TOKEN"
  ```

## Verification

1. Start Codex CLI; the /mcp command lists the configured servers, ovhcloud among them.
2. Ask Codex:
  ```text
  Which OVHcloud API operation reboots a dedicated server?
  ```

## References

- [Codex: MCP](https://developers.openai.com/codex/mcp)
- [mcp-remote, the bridge the configuration runs](https://github.com/geelen/mcp-remote)

[Next Gemini CLI →](https://developers.eu.ovhcloud.com/ai/mcp/gemini-cli.md)