Cloudways MCP: What It Reaches on a WordPress Site, and What It Doesn't
Updated October 31, 2026
The Cloudways MCP server is free for Cloudways customers and, after its 2.0 release, has more than 300 tools. Cloudways' MCP 2.0 post (updated October 16, 2026) gives that number, up from about 244. The older product page still says "250+ Cloudways actions," with 65 tools visible to your client at first.
None of those tools edits a post, a page or a menu. Cloudways built the MCP for the server and the WordPress install around your content.
| Cloudways MCP reaches | Not in Cloudways' published tools |
|---|---|
| Servers, apps, cloning, application logs | Posts, pages and custom post types |
| Cache purges, Varnish, CDN settings | Menus, widgets, templates, global styles |
| Plugins and themes: install, update, activate, delete | Elementor, Divi or Bricks layouts |
| Core updates in "safe updates" batches | SEO titles and meta descriptions |
| WordPress users, roles, password resets, SSO links | WooCommerce products and coupons |
| Vulnerability scans with severity scores | Theme file edits in a draft theme |
Cloudways lists Claude, Cursor, ChatGPT, Codex, VS Code, Gemini, Windsurf and Cline as clients. You connect with a scoped access token (full, read-only or per-endpoint, with an expiry), and since October 15, 2026 that's the only way in: API keys and the v1 API URL stopped working that day.
Some of the WordPress tools belong to Cloudways Site Manager. Its Free plan covers basic plugin, theme and user management, and Pro costs $3 per app per month for activity logs, auto-update tools and performance scoring. Bulk tools accept up to 300 apps in one call.
"May ask your permission"
Cloudways' product page says destructive actions require confirmation. Its newer MCP 2.0 post is more careful: "In some cases, your agent may ask your permission before executing a destructive action." It then tells you not to rely on that and to scope your token properly instead.
That's honest advice, and it shows where the check lives: inside the AI client, which decides when to ask.
Kitepod puts the check outside the AI. A user or role change, a plugin deletion, a database write or a core update waits for a person to approve it in Kitepod, and the assistant can't approve its own request. Under the default preset, plugin installs and updates wait too. More on how that works on the WordPress MCP page.
Two MCPs in one conversation
Kitepod covers the right-hand column of that table. It's a free remote MCP server plus a WordPress plugin, and the AI is your own Claude or ChatGPT, since Kitepod doesn't run a model.
Add both servers to the same assistant and a single request can use each for what it's good at:
Change the delivery cutoff on my Shipping page from 2pm to 3pm, then purge all caches for this app on Cloudways.
Kitepod edits the page and records it as an undoable change for 90 days. The Cloudways MCP purges the app's caches. Then Kitepod opens the live page and screenshots it so you can see the new cutoff.
Plugin updates are the one place they overlap. For one site, Kitepod takes a checkpoint before each update and can roll it back. For 80 client sites, Cloudways' bulk safe-update tools were built for exactly that.
Varnish and Breeze
Cloudways runs Varnish in front of WordPress, plus Redis or Memcached for objects, and ships its own Breeze cache plugin. Cloudways' Varnish guide says Breeze can run Varnish operations from inside WordPress.
To purge on the platform side, Cloudways points to Server Management → Manage Services, where Varnish can be purged or disabled. Cloudways' agency examples also show the MCP purging "all caches" for one WordPress site, which is quicker if you've already connected it.
Logging in from Access Details
- In the Cloudways platform, open the application and find the Admin Panel link under Access Details. It opens the wp-admin login. Then upload the Kitepod plugin zip at Plugins → Add New → Upload (requires WordPress 6.4+ and PHP 7.4+, plus outgoing HTTPS from the server).
- Click Connect, sign in to Kitepod and pick the WordPress account the AI will use.
- Add
https://kitepod.com/mcpas a custom connector in Claude (Claude setup) or as a custom MCP server in ChatGPT, then allow access.
If the site goes down hard enough that the Kitepod plugin can't respond, Kitepod can't help. The Cloudways MCP can still read the app's logs from outside WordPress, which makes it the better first stop.
Finer points
Is the Cloudways MCP server free?
Cloudways says it's available to all Cloudways customers at no extra charge. Some WordPress tools sit in Site Manager Pro at $3 per app per month.
Can the Cloudways MCP edit WordPress posts or pages?
No. It works on servers, caches, plugins, themes, users, updates and scans. Content needs a WordPress-side MCP.
Why did my Cloudways MCP connection stop working in October 2026?
API key access ended on October 15, 2026. Create an access token in the Cloudways dashboard and update your client.
Is Cloudways Copilot the same as the MCP?
No. Copilot is Cloudways' own AI that watches servers and apps, explains problems and applies fixes through SmartFix, paid in credits. The MCP lets your assistant call Cloudways' API.