Ploi.io MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLOI_API_TOKEN | Yes | Your Ploi API token. | |
| PLOI_USER_AGENT | No | Override the user agent sent to Ploi. | ploi-mcp-server/1.0.0 |
| PLOI_API_BASE_URL | No | Override the API base URL. | https://ploi.io/api |
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 |
|---|---|
| ploi_list_serversA | Retrieve a paginated list of all servers in the authenticated Ploi account. |
| ploi_get_serverA | Retrieve details for a single Ploi server. |
| ploi_create_serverA | Create a new provider-backed Ploi server. Use account provider tools first to discover valid credentials, plans, and regions. |
| ploi_create_custom_serverA | Create a custom server record and return the SSH command/start URL required to begin installation. |
| ploi_start_custom_server_installationA | Start installation for a custom Ploi server after the returned SSH command has been run. |
| ploi_update_serverB | Update server metadata such as name, IP address, and SSH port. |
| ploi_restart_serverB | Reboot a Ploi server. |
| ploi_delete_serverA | Delete a Ploi server. This is irreversible and removes associated data. |
| ploi_list_sitesA | Retrieve a paginated list of all sites on a Ploi server. |
| ploi_get_siteA | Retrieve details for a single site on a Ploi server. |
| ploi_create_siteB | Create a new site on a Ploi server. |
| ploi_update_siteA | Update site properties. Domain changes are processed asynchronously by Ploi. |
| ploi_delete_siteA | Delete a site from a Ploi server. |
| ploi_deploy_siteA | Trigger or schedule a deployment using the site's configured deploy script. |
| ploi_get_site_nginx_configurationA | Retrieve the NGINX configuration for a Ploi site. |
| ploi_update_site_nginx_configurationA | Replace the NGINX configuration for a Ploi site. Ploi may require a reload/restart afterward. |
| ploi_list_databasesA | Retrieve a paginated list of databases on a Ploi server. |
| ploi_get_databaseA | Retrieve details for a single database on a Ploi server. |
| ploi_duplicate_databaseA | Clone an existing database to a new database on the same server. |
| ploi_forget_databaseA | Remove a database from Ploi records without deleting it from the server. |
| ploi_list_containersA | Retrieve a paginated list of Docker containers on a Ploi server. |
| ploi_get_containerA | Retrieve details for a single Docker container on a Ploi server. |
| ploi_create_containerB | Create a Docker application container on a Ploi server. |
| ploi_update_containerA | Update a Docker container name or compose deploy script. |
| ploi_start_containerB | Queue a Docker container for startup on a Ploi server. |
| ploi_stop_containerA | Queue a Docker container for shutdown on a Ploi server. |
| ploi_restart_containerA | Queue a Docker container shutdown followed by startup using Ploi's documented down/up endpoints. |
| ploi_delete_containerB | Delete a Docker container from a Ploi server. |
| ploi_list_server_providersA | List server provider credentials linked to the authenticated Ploi account. |
| ploi_get_server_providerA | Retrieve a server provider credential, including available plans and regions. |
| ploi_list_backup_configurationsB | List backup configurations linked to the authenticated Ploi account. |
| ploi_get_ip_addressesA | Retrieve Ploi IP addresses for allow-listing workers and uptime checks. |
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 32 tools
Each tool targets a distinct resource and action. Categories like servers, sites, databases, and containers have clear boundaries with no overlapping operations.
All tools follow a consistent 'ploi_verb_noun' pattern (e.g., ploi_list_servers, ploi_create_site), making it easy to infer function from name.
With 32 tools, the set is on the high side but still reasonable for managing multiple server aspects (servers, sites, databases, containers, providers, backups, IPs). A slight reduction could improve focus.
The tool surface covers servers, sites, and containers well, but databases lack create/delete operations and backups only list configurations. Notable gaps for a server management tool.