empaya-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDWAYS_EMAIL | Yes | Your Cloudways account email | |
| CLOUDWAYS_API_TOKEN | Yes | Your Cloudways API token | |
| CLOUDWAYS_LOG_LEVEL | No | Log level (e.g., info, debug) | info |
| CLOUDWAYS_API_BASE_URL | No | Base URL for Cloudways API | https://api.cloudways.com/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-cloudways-serversB | List Cloudways servers with optional status filtering. |
| list-cloudways-appsC | List applications for a Cloudways server. |
| get-server-statsC | Fetch CPU, RAM, disk, uptime, and load information for a Cloudways server. |
| deploy-cloudways-appC | Start a Git deployment for a Cloudways application. |
| check-deployment-statusC | Check progress and logs for a Cloudways deployment. |
| get-cloudways-logsC | Read recent Cloudways application, error, access, or deployment logs. |
| set-environment-variableC | Set or update an environment variable for a Cloudways application. |
| list-environment-variablesA | List Cloudways environment variable names without exposing sensitive values. |
| manage-ssl-certificateC | List, enable automatic SSL, or install a custom SSL certificate for an app. |
| create-cloudways-backupC | Create an on-demand backup for a Cloudways application. |
| list-cloudways-backupsC | List backups and their metadata for a Cloudways application. |
| restart-cloudways-serviceC | Restart a Cloudways server service. Endpoint may need adjustment for Cloudways API V2. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose covering different Cloudways management tasks (deployment, backups, logs, environment variables, SSL, etc.). No two tools appear to do the same thing.
All names use snake_case and start with a verb, but there is some inconsistency in whether 'cloudways' is included in the noun (e.g., 'list-cloudways-apps' vs 'check-deployment-status'). Overall the pattern is mostly predictable.
12 tools is appropriate for a Cloudways management server. Each tool covers a necessary operation without unnecessary bloat, and the number is within the ideal 3-15 range.
The tool surface covers major workflows like listing, deploying, backups, logs, SSL, and environment variables. Minor gaps exist (e.g., no delete backup or delete environment variable), but overall it is largely sufficient for common tasks.