Gemini CLI + Cloudways
Cloudways MCP Gemini CLI Setup: settings.json, Headers and Test Prompts
Gemini CLI can connect directly to the remote Cloudways MCP server through ~/.gemini/settings.json. The detail most likely to trip people up is that Cloudways documents httpUrl for Gemini's Streamable HTTP connection. Using url instead can make Gemini attempt a different transport.
Use the generator below to create the correct JSON structure with a token placeholder, then replace that placeholder locally with a scoped Cloudways access token.
Interactive tool
Cloudways MCP Configuration Generator
Choose your AI client and intended permission level. The generator uses a token placeholder only. Your real Cloudways access token should be inserted locally in your client configuration.
Quick answer
What is the correct Cloudways MCP setting for Gemini CLI?
Inside mcpServers.cloudways, use httpUrl set to https://mcp.cloudways.com/mcp/ and add headers for X-Access-Token and X-Mcp-Host: gemini-cli. Save ~/.gemini/settings.json and start Gemini so it can discover the Cloudways tools.
Do not copy Cursor's url key into Gemini's configuration. Cloudways specifically warns that Gemini CLI uses httpUrl for the Streamable HTTP server.
Gemini CLI Cloudways MCP settings
Use these exact client-specific values before debugging anything deeper.
| Setting | Correct value | Why |
|---|---|---|
| Config file | ~/.gemini/settings.json | Gemini CLI reads MCP servers from its settings file. |
| URL key | httpUrl | Cloudways warns that url can trigger the wrong connection type. |
| Endpoint | https://mcp.cloudways.com/mcp/ | Official Cloudways MCP remote endpoint. |
| Access header | X-Access-Token | Use a scoped Cloudways token. |
| Host header | X-Mcp-Host: gemini-cli | Identifies the MCP host to Cloudways. |
| First test | List my Cloudways servers | Confirms authentication with a read-only request. |
Before you connect an AI client to Cloudways
Start with READ
Validate discovery and account visibility before granting modification rights.
Use a dedicated token
Create a separate token for each AI client so access can be rotated or revoked independently.
Keep secrets local
Never paste a real Cloudways access token into public pages, screenshots, repositories, or support posts.
Be precise on production
Name the target server, application, environment, and intended action before allowing a write operation.
Generate a dedicated token for Gemini CLI
Use Cloudways API Integration to create an access token specifically for Gemini CLI. A distinct token makes it easier to rotate credentials, review scope, and remove access later without breaking other AI clients.
Start with READ permission. If Gemini will execute a defined deployment or management workflow, switch to a Limited Scope token that covers only the needed endpoint groups.
Why httpUrl matters in Gemini
MCP clients do not all use the same configuration keys. Cloudways documents httpUrl for Gemini CLI because it represents the Streamable HTTP server. A generic url key can cause Gemini to attempt an SSE connection instead, which means a configuration copied from another client can fail even though the endpoint is correct.
This is exactly why the Cloudzat generator changes output by client rather than showing one universal JSON block.
Validate discovery with a read-only prompt
After saving settings.json, launch Gemini CLI and ask for a list of your Cloudways servers. Follow with a more specific request for applications, versions, or monitoring data. These tests establish that the remote server, token, and host header are all working.
If a recently released Cloudways tool is missing, restart or reconnect the MCP server so Gemini refreshes the tool list rather than relying on a cached version.
Use Gemini CLI for repeatable hosting operations
The integration is useful when a command-line workflow needs hosting context without a separate dashboard session. You can inspect Cloudways resources, reason about an application issue, and then invoke a supported operation from the same terminal-oriented assistant.
Production automation should still be bounded by token scope and explicit prompts. Avoid giving a general-purpose CLI agent Full Access simply because one workflow needs a single write action.
Troubleshoot Gemini Cloudways MCP
If Cloudways tools do not appear, first validate the JSON and the httpUrl key. Then confirm that the token has not expired, the X-Mcp-Host value is gemini-cli, and the endpoint includes the /mcp/ path.
If authentication was migrated from the older API key method, remove obsolete credentials so future troubleshooting is not confused by two competing setups.
Methodology and primary sources
Cloudzat checks client-specific configuration details against Cloudways' own MCP documentation and uses vendor documentation for plan-dependent client behavior. Last verification date: August 26, 2026.
Frequently asked questions
Does Gemini CLI use url or httpUrl for Cloudways MCP?
Cloudways currently documents httpUrl. Its setup guide notes that using url can attempt an SSE connection instead.
Where is the Gemini CLI MCP configuration file?
Cloudways documents ~/.gemini/settings.json.
What X-Mcp-Host value should Gemini CLI use?
Use gemini-cli.
How do I know the Cloudways connection works?
Start Gemini CLI and ask for a read-only Cloudways inventory result, such as listing your servers. If it can return account-specific infrastructure data, the MCP connection is working.
Cloudzat may earn a commission if you sign up for Cloudways through links on this page. This does not change your price. Product capabilities, plan availability, promotions, and MCP client interfaces can change; verify critical production settings before acting.