VS Code + Cloudways
Cloudways MCP VS Code Setup: mcp.json, Copilot and Access Token
VS Code uses a different MCP JSON shape from Cursor. Cloudways currently documents a servers object, type set to http, the official MCP URL, and a headers block with X-Access-Token and X-Mcp-Host: vs-code. Copying Cursor's mcpServers format into VS Code is a common avoidable mistake.
The generator below produces the VS Code-specific structure and a test checklist without asking you to enter a real access token on Cloudzat.
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
How do you add Cloudways MCP to VS Code?
Open the MCP server flow from the VS Code Command Palette, add the Cloudways HTTP endpoint, then use the Cloudways-documented mcp.json structure with servers.cloudways, type: http, the endpoint, and the required access-token and host headers.
After saving the file, restart the Cloudways server entry and confirm that it shows as running in the MCP Servers area before testing a read-only prompt in Copilot Chat.
VS Code Cloudways MCP configuration reference
VS Code's JSON keys are not identical to Cursor's.
| Setting | VS Code value | Watch for |
|---|---|---|
| Root key | servers | Do not use Cursor's mcpServers root in the documented VS Code format. |
| Type | http | Cloudways documents an explicit HTTP type. |
| URL | https://mcp.cloudways.com/mcp/ | Use the official endpoint. |
| Token header | X-Access-Token | Use a scoped Cloudways access token. |
| Host header | X-Mcp-Host: vs-code | Use the VS Code host identifier. |
| Restart | Restart server entry | Refreshes the connection and tool discovery after changes. |
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 Cloudways token before opening VS Code
Create a named access token in Cloudways API Integration. Use READ permission for the first connection and only introduce write scopes when your VS Code workflow actually needs them.
A separate token for VS Code is easier to revoke than reusing one credential across every AI client. It also makes it clearer which integration is responsible when you audit or rotate access.
Use the VS Code-specific MCP JSON structure
Cloudways' current instructions use a servers object with a cloudways entry, type http, url, and headers. The file may be opened through the MCP: Add Server flow and then edited so the headers match Cloudways requirements.
The generator intentionally keeps the token as a placeholder. Replace it locally and avoid sending a real token to paste sites, public validators, or support screenshots.
Verify Cloudways in Copilot Chat
After saving the MCP configuration, restart the Cloudways server entry and confirm that VS Code reports it as running. Then use Copilot Chat to ask for a simple Cloudways inventory result before attempting a write action.
If the server is configured but a tool is missing, refresh the MCP connection. Cloudways notes that clients can cache the tool list and may not immediately show newly released capabilities.
Good VS Code Cloudways workflows
VS Code is a natural place to combine application code with hosting operations. A developer can inspect a repository, reason about a deployment, check Cloudways state, work with staging or Git, and verify post-deployment behavior without moving through several interfaces.
For production, keep prompts explicit and scope the token narrowly. The fact that Copilot can call a tool does not mean every available tool should be enabled for every developer or repository.
Fix common VS Code connection errors
If the server does not start, check that the file uses servers rather than mcpServers, type is http, the endpoint is exact, and both Cloudways headers are present. Confirm that the access token is current and has the expected scope.
If VS Code displays a dynamic client registration prompt while adding the server, follow the current Cloudways setup guidance and then replace the configuration with the documented header-based JSON.
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 VS Code use the same MCP JSON as Cursor?
No. Cloudways currently documents a servers root with type: http for VS Code, while Cursor uses mcpServers.
What X-Mcp-Host value should VS Code use?
Use vs-code as documented by Cloudways.
Where do I test the Cloudways MCP connection in VS Code?
Confirm the MCP server is running, then use Copilot Chat to request a read-only Cloudways result such as your server list.
Why are new Cloudways tools missing in VS Code?
The MCP tool list may be cached. Restart or refresh the Cloudways MCP server so VS Code discovers the current tool set.
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.