# Gemini 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 Gemini 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

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

## Configuration

1. Open ~/.gemini/settings.json, or create it.
2. Add the OVHcloud server, and replace YOUR_OVHCLOUD_TOKEN with your token:
  ```json
  {
  "mcpServers": {
    "ovhcloud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.eu.ovhcloud.com/mcp",
        "--header",
        "Authorization:${OVH_AUTH_HEADER}"
      ],
      "env": {
        "OVH_AUTH_HEADER": "Bearer YOUR_OVHCLOUD_TOKEN"
      },
      "trust": false,
      "timeout": 600000
    }
  }
}
  ```

## Verification

1. List the servers; ovhcloud should appear:
  ```bash
  gemini mcp list
  ```
2. Ask Gemini:
  ```text
  Which OVHcloud API operation reboots a dedicated server?
  ```

## References

- [Gemini CLI: MCP servers](https://github.com/google-gemini/gemini-cli/blob/main/docs/tools/mcp-server.md)
- [mcp-remote, the bridge the configuration runs](https://github.com/geelen/mcp-remote)

[Next OpenCode →](https://developers.eu.ovhcloud.com/ai/mcp/opencode.md)