Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The migration was announced with MCP v1.2 on July 16. Reaching its stated date is not a new launch or a shutdown of every Cloudways API key.
- READ supports queries; Full Access includes changes and deletion. Limited Scope restricts selected endpoints or endpoint groups.
- New configurations use X-Access-Token and X-Mcp-Host. Regenerating an old API key does not replace this migration.
- Reconnect after saving, then check the connection and permitted tools. Connected does not mean every action is authorized or completed.
What deadline did Cloudways announce?
The July 16, 2026 MCP v1.2 announcement says old API keys stop working after October 14. The help center says deprecated by October 15 and points to X-Access-Token. Neither supplies a cutoff hour or time zone; complete the MCP authentication change promptly.
This concerns the old Cloudways MCP authentication method. It does not announce retirement of every Cloudways API key or establish whether a particular account has already been disconnected. A working old connection is not a promise of continued support.
Start with READ when you only need answers
An access token can limit permissions. READ allows information retrieval; Full Access permits changes and deletion. Limited Scope allows selected endpoints or endpoint groups. Identify the required action before granting more access.
Hypothetical, not executed: a team listing applications can start with READ. A later settings change needs its own tool, target and permission review. Do not grant full access just to populate a tool list. Read access still exposes account information that should not be shared publicly.
Prepare a new token in your account
First, use an account you are authorized to manage. In the account area previously used for API keys, locate Access Token and select READ or the required limited scope. The announcement does not document every current button; the legacy Regenerate API Key instruction is not proof that it creates a new token.
Next, locate the Cloudways MCP entry your client actually uses. Put the new token only in its credential configuration, not a conversation, screenshot or public repository. Relabeling an old key does not turn it into an access token.
Replace the headers in the correct client format
The documented endpoint is https://mcp.cloudways.com/mcp/, including the trailing slash. X-Access-Token carries the token; X-Mcp-Host identifies the actual client. This changes MCP connection credentials without requiring a Cloudways server restart.
For Cursor native HTTP, edit ~/.cursor/mcp.json. Preserve other entries. Under mcpServers, find cloudways: set url to that endpoint and set headers to include X-Access-Token with the new token and X-Mcp-Host with cursor. Save valid JSON.
Use the official client-specific example elsewhere. VS Code uses servers and type:http; Gemini CLI uses httpUrl. Copying Cursor’s entire structure across clients can select the wrong format or transport. Full examples are linked in Sources.
Reconnect the client, then check its result
Toggle the Cloudways MCP entry off and on. If unavailable, fully quit and reopen the client; closing a window may leave it running. This refreshes the connection and tool cache. It is not server_restart or service_restart.
Check connection status and discovered tools. Cursor’s guide uses a green indicator. Permissions still determine available actions. If checking a query, use only authorized resources and compare the returned account, server or application with the intended target.
Keep connection checks separate from changes
The tool catalog distinguishes server_list and service_status queries from server_delete, which permanently removes a server and its data, and service_restart. Do not use deletion, scaling or restarts as a connection test.
Confirm connectivity, then the required query. Deployments, service changes and deletion require their own authorization. A catalog describes capabilities, not actions already performed or guaranteed business results.
Sources
Frequently Asked Questions
Why does the guide still mention email and an API key?
Legacy steps and FAQs coexist with newer Required Headers and token-based examples. Follow the new configuration when migrating. Ask Cloudways Support about mismatched account controls rather than treating the legacy method as a lasting alternative.
Does a shorter tool list mean the token is invalid?
Not necessarily. The announcement describes dynamic tool discovery, while clients can cache older lists. Check reconnection, the specific tool and its permitted scope before concluding authentication failed or granting more access.
Does a 401 mean I should regenerate every account key?
Check the actual MCP entry, new token, header names and saved configuration first. A 401 alone neither proves all account keys expired nor establishes that the announced cutoff has been enforced for your account.
Can I keep the old configuration as a fallback if the new token fails?
The announced retirement means a working legacy connection is not a promise of continued support. Retain error details without token values and check the new configuration. Ask Cloudways Support if the token controls are missing or the connection still fails, rather than broadening permissions to restore access.