Cursor + Cloudways
Cloudways MCP Cursor Setup: mcp.json, Access Token and Test Prompts
Cursor has one of the most straightforward Cloudways MCP configurations. Cloudways documents a native remote HTTP setup in ~/.cursor/mcp.json using the official MCP URL and two headers: X-Access-Token and X-Mcp-Host. If the native connection is blocked by a proxy or other local issue, Cloudways also documents an mcp-remote fallback.
The generator below creates the native configuration with a token placeholder, shows the expected file path, and gives you safe test prompts. Your real Cloudways token is never required on this page.
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 should the Cursor Cloudways MCP config contain?
Use an mcpServers entry named cloudways with url set to https://mcp.cloudways.com/mcp/, X-Access-Token set to your scoped token, and X-Mcp-Host set to cursor. Save the file, return to Cursor's Tools & MCP settings, and verify that the Cloudways server is active.
If Cursor shows a red indicator, first validate the JSON and token. Use the mcp-remote bridge only as a fallback when the native HTTP configuration does not work in your environment.
Cursor Cloudways MCP configuration reference
A small number of exact values account for most setup failures.
| Setting | Value | Common mistake |
|---|---|---|
| Config file | ~/.cursor/mcp.json | Editing a different project or application config file. |
| URL key | url | Using serverUrl or httpUrl, which belong to other clients. |
| Endpoint | https://mcp.cloudways.com/mcp/ | Dropping or changing the official MCP path. |
| Token header | X-Access-Token | Using the deprecated API-key flow for a new setup. |
| Host header | X-Mcp-Host: cursor | Using a host value intended for Codex, Gemini, or Claude. |
| Fallback | mcp-remote | Using the bridge before testing Cursor's native HTTP configuration. |
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 a scoped token before editing Cursor
Generate a Cloudways access token from API Integration and begin with READ permission. This is enough for connection testing and reduces the consequence of a copied token, a mistaken prompt, or a tool call you did not intend to authorize.
If Cursor will perform a deployment or another change, create a Limited Scope token around that workflow instead of giving the coding environment blanket access to unrelated Cloudways operations.
Use Cursor's native HTTP MCP configuration first
Cloudways' preferred Cursor setup uses a standard mcpServers JSON object with a remote URL and headers. Cursor should detect the server after the file is saved. In the Tools & MCP area, the connection should show as available rather than remaining red or disconnected.
The configuration generator keeps the token as a placeholder so you can copy the structure and insert your secret locally. Avoid pasting production tokens into online JSON validators or public issue trackers while troubleshooting syntax.
When to use mcp-remote
Cloudways documents an mcp-remote alternative for connection problems such as proxy restrictions. That method uses npx to bridge the remote MCP server through stdio and therefore adds a Node.js dependency that the native Cursor HTTP configuration does not require.
Treat it as a compatibility fallback, not the default. Fewer moving pieces generally means fewer places for credentials, package execution, path configuration, or runtime versions to fail.
Best Cursor prompts after setup
Start by asking Cursor to list Cloudways servers or show applications on a selected server. Once read access is proven, a developer can use MCP while investigating code, deployment state, PHP settings, Git workflows, or service configuration.
For write tasks, be explicit about the target application and environment. A prompt that names the exact staging application and desired action is safer than a broad instruction such as fix everything on my Cloudways account.
Fix missing tools and stale capability lists
Cloudways notes that MCP clients cache their tool lists. If Cloudways adds a new capability and Cursor cannot find it, disable and re-enable the Cloudways MCP server or fully restart Cursor so it discovers the current tools.
If the server itself will not connect, troubleshoot JSON syntax, endpoint accuracy, token validity, token expiry, and host header before assuming a specific Cloudways tool is broken.
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
What file does Cursor use for Cloudways MCP?
Cloudways currently documents ~/.cursor/mcp.json for the manual Cursor setup.
What is the Cursor X-Mcp-Host value?
Use cursor exactly as documented by Cloudways.
Do I need Node.js for the normal Cursor setup?
Not for Cloudways' native Cursor HTTP configuration. Node.js is needed if you use the documented mcp-remote fallback.
Why does Cursor show Cloudways MCP with a red dot?
Check JSON syntax, the official endpoint, your access token, and the required headers. Restart Cursor after correcting the configuration.
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.