Claude Code + Cloudways
Cloudways MCP Claude Code Setup: Commands, Headers and Test Prompts
Claude Code is one of the cleanest Cloudways MCP integrations because it supports a remote HTTP MCP server directly from the CLI. You do not need to hand-edit a JSON file for the basic setup. The important details are the Cloudways endpoint, the X-Access-Token header, the X-Mcp-Host value of claude-code, and the permission scope of the token you create.
Use the configuration generator below to produce the current command and a validation checklist. It deliberately keeps your real token out of the page and uses a placeholder that you replace locally in your terminal.
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 command connects Claude Code to Cloudways MCP?
Cloudways currently documents Claude Code with the claude mcp add command using HTTP transport, the Cloudways access token header, X-Mcp-Host: claude-code, user scope, and the official https://mcp.cloudways.com/mcp/ endpoint.
After adding it, run claude mcp list and then test a read-only prompt. If the connection is new, use a READ token first rather than a Full Access token.
Claude Code Cloudways MCP settings
These values should match Cloudways' current client-specific documentation.
| Setting | Value | Notes |
|---|---|---|
| Transport | http | Claude Code supports the remote HTTP server directly. |
| Server | https://mcp.cloudways.com/mcp/ | Use the official Cloudways MCP endpoint. |
| Auth header | X-Access-Token | Replace the placeholder locally with your scoped token. |
| Host header | X-Mcp-Host: claude-code | Use the exact host identifier documented by Cloudways. |
| Scope flag | -s user | Stores the MCP configuration at user scope across projects. |
| Verify | claude mcp list | Confirms the server is registered before you test a prompt. |
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.
Create the right Cloudways access token
Create the token in Cloudways API Integration and give it a descriptive name so you know it belongs to Claude Code. For initial testing, READ is enough to list servers, inspect applications, and verify the integration without allowing modifications.
When you need deployments or other changes, create a Limited Scope token for the required endpoint groups. This keeps a coding assistant from having unrelated infrastructure permissions simply because it can perform one useful deployment task.
Install the MCP connection at user scope
Cloudways' current example uses Claude Code's native remote HTTP transport and the -s user flag. That is useful when you want the same Cloudways connection available across projects rather than recreating it in each repository.
Keep the access token out of tracked project files. If a token is accidentally committed, rotate it in Cloudways and remove it from repository history rather than assuming a later deletion is sufficient.
Verify before running write actions
Run claude mcp list after adding the server. Then open Claude Code and ask for your Cloudways server list or a selected application's configuration. If discovery works but a specific new tool appears missing, reconnect the MCP server so the client refreshes the cached tool list.
A successful inventory request is a better first test than a deployment because it isolates authentication and tool discovery from the extra variables involved in changing production infrastructure.
Useful Claude Code and Cloudways workflows
The combination is strongest when a code change and an infrastructure action are part of the same task. You can inspect an application, reason about a deployment, work with Git, review PHP or service settings, and then execute a supported Cloudways action without leaving the development environment.
For production use, define which changes Claude Code may execute automatically and which require a human confirmation. Backups, staging, SSL, malware, firewall, and deployment tools can all have very different risk profiles.
Troubleshooting Claude Code MCP
If Claude Code cannot initialize Cloudways MCP, check the endpoint, token, host header, and whether the CLI stored the server at the expected scope. Cloudways also recommends refreshing the MCP connection when tools are stale after an MCP update.
If you are migrating from an older API-key configuration, replace it with a scoped access token before the legacy API key reaches end of life. Avoid keeping both methods active longer than necessary.
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 Claude Code need mcp-remote for Cloudways?
No. Cloudways currently documents Claude Code using its native remote HTTP MCP support. Claude Desktop is the client that Cloudways documents with an mcp-remote bridge.
What X-Mcp-Host value should Claude Code use?
Cloudways documents the value claude-code for Claude Code.
How do I check that Cloudways MCP was added?
Run claude mcp list, then test a read-only Cloudways prompt such as listing your servers.
Can I use the same token for every Claude project?
Technically a user-scoped connection can be available across projects, but the safer design is to keep the token permissions limited to the operations you actually need and rotate credentials when exposure changes.
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.