Application Development
Cloudways MCP connector
The Cloudways connector brings your Cloudways servers and hosted apps into Claude, ChatGPT, Cursor and other AI clients, so your team can list, launch, clone, scale, restart and retire them by asking, with every action logged under the person who asked.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Cloudways to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Cloudways once
-
Open Connections, choose Add connection, and pick Cloudways.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Cloudways API key. One person generates a token in Cloudways and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Cloudways to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Cloudways to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Cloudways to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Cloudways to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Cloudways through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Restart a stalled server without opening a console
When a client site stops responding, ask which Cloudways server it lives on and restart it in the same conversation. The audit log records who did it and when.
-
Engineering
Clone production to build a staging copy
Ask for a clone of the production server before a major release, then point the team at the copy. No hunting through the Cloudways dashboard for the right server.
-
Client services
Launch a new client site on an existing server
Pick the server, choose the application package, and create the app in one ask. The agent checks available packages and settings first so the new site starts with the right options.
-
Operations
Scale up before a launch, back down after
Ask to scale a Cloudways server or grow its storage volume ahead of a campaign, then bring it back down once traffic settles.
-
Finance
See every server, size, provider and region
Ask for a list of running Cloudways servers with their sizes and cloud providers, then spot the ones nobody has used in months and stop or delete them.
-
Marketing
Retire a campaign microsite cleanly
When a landing page has done its job, find the app on its Cloudways server and remove it, or stop the whole server if nothing else runs there.
Try asking
- “Which apps are running on our staging servers.”
- “List backups scheduled this week across all apps.”
- “Show server sizes available in the Frankfurt region.”
AI tools
Cloudways tools for your AI agents
339 tools are ready to call through Elaichi's MCP endpoint the moment you connect Cloudways, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Cloudways gets you
6 screens from the product, each doing one job for your Cloudways account.
The agent
Ask Cloudways questions, get real answers.
Type a question in plain language and get answers pulled from live Cloudways records.
- apps
- servers
- backups
- packages
Ask Elaichi to work across your apps.
Which apps are running on our staging servers.
List backups scheduled this week across all apps.
Show server sizes available in the Frankfurt region.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, every client, no shared keys.
Claude, ChatGPT and Cursor all connect to Cloudways through one governed org endpoint.
Copy the endpoint
Tool catalog
339 Cloudways tools, zero custom code.
Every Cloudways method and resource is cataloged and ready to call, no code required.
- Create a Cloudways oauth access token
- List all Cloudways providers
- List all Cloudways regions
- List all Cloudways server sizes
Toolboxes
Every team gets its own Cloudways toolbox.
Toolboxes scope Cloudways access separately for each team that needs it.
- Platform Engineering
- DevOps
- Product
- Support
Shared connections
Delegate Cloudways access without sharing passwords.
Teammates work through a shared Cloudways connection without ever seeing the credential.
- Production Hosting
- Staging Environment
- Client Sites
- Agency Ops
Audit log
Every Cloudways action, logged and traceable.
See who did what on Cloudways, when it happened and which resource it touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule triggers real Cloudways work end to end.
Records are fetched, grouped, drafted, approved by a person, then posted back to Cloudways.
Cloudways digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch apps
Cloudways
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Cloudways
Queued
Collections and dashboards
Cloudways health, computed on a schedule, not asked for.
Metrics and a 14 day chart of records show Cloudways activity broken down by team.
Cloudways health
Refreshed 4 minutes ago · every 15 minutes · from the apps collection
Apps
1,284 ↓ 12%
Servers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Apps created
Last 14 days
By team
Share of activity
Production Hosting 34%
Staging Environment 27%
Client Sites 21%
Agency Ops 18%
FAQ
Frequently asked questions
How do I connect Cloudways to Claude?
Two steps. In Elaichi, add the Cloudways connector and paste the API key from your Cloudways account settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi login and Cloudways is available in your next conversation.
Does Cloudways work with ChatGPT and Cursor as well as Claude?
Yes. Once Cloudways is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client. You connect Cloudways once and every client you sign into picks it up.
What can an AI agent actually do with my Cloudways account?
It can list your Cloudways servers and the apps hosted on them, create new servers or apps, clone a server, start, stop or restart one, and scale a server's size or storage volume. It can also look up the providers, regions, server sizes, packages, backup frequencies and monitoring options Cloudways offers before it acts. Because Cloudways exposes a large set of actions, short concrete asks like "restart the server hosting the Acme site" work better than long paragraphs.
Does connecting Cloudways give the AI access to every server in my account?
The AI only sees what the person who signed in can see. If your Cloudways API key belongs to an account with three servers, that is what the agent can reach, and Elaichi can narrow that further, for example to listing and restarting only. Elaichi never grants more than the connected Cloudways account already holds.
Can I stop an agent from deleting or changing things in Cloudways?
Yes. Restrictions in Elaichi work per action, so you can allow listing servers and apps while blocking deletion, scaling or shutting down a Cloudways server. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, accidental or otherwise, can reach it.
What happens to a Cloudways connection when someone leaves?
Offboarding that person in Elaichi ends their access to Cloudways at once, across every AI client they used. A shared Cloudways connection keeps working for everyone else on the team. If you want to remove Cloudways entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Put Cloudways in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.