Cloudways AI Infrastructure
Cloudways MCP: Connect AI to Your Hosting Infrastructure
Cloudways MCP lets an MCP-compatible AI client work with your Cloudways account through natural-language requests. Instead of opening the hosting dashboard for every routine task, you can ask an AI client to inspect servers, work with applications, manage deployments, review monitoring data, handle security tasks, and use other Cloudways capabilities exposed through MCP.
The important part is not simply connecting the endpoint. A useful setup needs the correct client format, a scoped Cloudways access token, the required MCP host header, a low-risk first test, and a clear rule for when the AI is allowed to make changes. The configuration generator below builds the client-specific starting point without asking you to paste a real access token into this website.
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 fastest safe way to start with Cloudways MCP?
Create a Cloudways access token with READ permission first, connect the official endpoint at https://mcp.cloudways.com/mcp/, use the client-specific X-Mcp-Host value, then test with a read-only prompt such as asking for a list of your servers. Move to a Limited Scope token only when you know which actions you want the AI client to perform.
Cloudways says MCP is included for Cloudways customers and its current product page markets more than 250 infrastructure actions. The July 2026 v1.2 release described roughly 244 tools, with a smaller set loaded directly and additional tools discovered through meta-tools.
Cloudways MCP setup at a glance
These are the values that matter before you start configuring a client.
| Item | Recommended value | Why it matters |
|---|---|---|
| MCP endpoint | https://mcp.cloudways.com/mcp/ | Use the official remote endpoint and keep the trailing slash. |
| Authentication | Cloudways Access Token | Scoped tokens replace the older all-powerful API key method. |
| First permission | READ | Lets you validate the connection without allowing infrastructure changes. |
| Required host header | X-Mcp-Host | Cloudways uses a client-specific host value such as cursor, codex, or gemini-cli. |
| First test | List my Cloudways servers | A simple inventory request verifies discovery and authentication without changing resources. |
| Legacy API key | Migrate away | Cloudways schedules the legacy API key method to reach end of life on October 15, 2026. |
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.
How Cloudways MCP changes the hosting workflow
Traditional managed hosting still requires a lot of dashboard movement. You open a server, locate an application, check a service, switch to monitoring, then move somewhere else for SSL, backups, Git, staging, Cloudflare, or security. MCP changes the interface layer. Your AI client can discover Cloudways tools and translate a clear request into the relevant Cloudways operation.
That does not turn the AI into an independent DevOps team. You still need to understand the impact of a restart, deployment, scaling action, firewall change, database operation, or deletion. The advantage is speed and context: the same client that is helping you debug an application can also inspect the infrastructure supporting it.
Use access tokens instead of the legacy API key
Cloudways introduced role-based access tokens for MCP so an integration no longer needs unrestricted account credentials. A READ token is appropriate for inventory, status checks, monitoring, and other observation tasks. A Limited Scope token is better when the assistant needs a defined group of actions. Full Access should be reserved for workflows where broad modification rights are genuinely required.
Treat every access token like a password. Cloudways shows the token when it is created, and the token should never be published in screenshots, documentation, support tickets, source control, or a public configuration example. This Cloudzat generator deliberately uses a placeholder instead of collecting your secret.
Why you may not see every Cloudways MCP tool at once
Cloudways v1.2 expanded MCP to roughly 244 tools, while the current Cloudways product page describes 250+ actions. Loading hundreds of tool definitions into every AI conversation would waste context, so Cloudways uses a smaller direct tool set plus meta-tools that can locate and execute additional capabilities when needed.
If a capability seems missing after Cloudways updates MCP, refresh or reconnect the MCP server in your client. Cloudways documents tool-list caching as a common reason a newly added action does not appear immediately.
Good first prompts after connecting
Start with prompts that only inspect your account. Ask for your server list, the applications on a selected server, the PHP version for an application, or current monitoring information. These requests confirm that the MCP client can authenticate, discover tools, and return data before you grant change permissions.
After that, test one narrow write workflow with a Limited Scope token. A staging operation, a controlled cache purge, or a deployment to a non-production application is a better first modification than a server deletion, credential change, or broad firewall operation.
Who gets the most value from Cloudways MCP
Agencies and developers have the clearest use case because they repeatedly move between code, troubleshooting, deployments, monitoring, and hosting administration. The same pattern is useful for technical site owners who want faster infrastructure checks without learning every Cloudways API endpoint.
The highest value comes when MCP becomes part of a repeatable operating workflow rather than a novelty. Define approved prompt patterns, use scoped tokens, separate production from staging, and document which actions require a human review before execution.
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
Is Cloudways MCP free?
Cloudways currently states that MCP is free for Cloudways customers. You still need a Cloudways account and the hosting or services you use remain billable under their normal pricing.
What is the Cloudways MCP server URL?
The official Cloudways MCP endpoint is https://mcp.cloudways.com/mcp/. Cloudways specifically documents the trailing slash in its setup and troubleshooting guidance.
Should I use a Cloudways API key or access token?
Use a scoped Access Token for new setups. Cloudways is deprecating the legacy API key authentication method and schedules it to reach end of life on October 15, 2026.
Can Cloudways MCP make changes to a production server?
It can perform supported write actions when the token and client permissions allow them. Start with READ access and use Limited Scope permissions for narrowly defined production workflows.
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.