Plesk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLESK_HOST | Yes | Base URL of your Plesk server. May include port. | |
| PLESK_API_KEY | No | API key for authentication (recommended). | |
| PLESK_PASSWORD | No | Password for authentication (alternative to API key). | |
| PLESK_USERNAME | No | Username for authentication (alternative to API key). Typically "admin". |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| api_list_tagsA | List available Plesk API tags. Start here to explore Plesk APIs. |
| api_listB | List available Plesk APIs. |
| api_helpA | Explain how to call a specific Plesk API. |
| api_callA | Call Plesk API. Do not use any preconceived notions about how to use Plesk API. Instead validate usage with api_help tool. |
| execA | Executes a command on the Plesk server and returns the result. The command CWD is the home directory of the user
(e.g. This tool will fail for subscriptions with no or chrooted shell access ( |
| uploadA | Uploads a file with the given content to the Plesk server and returns the file path. The file will be uploaded to a temporary location returned by this tool and can be used in subsequent commands.
The file is uploaded as |
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 6 tools
Each tool has a distinct purpose: API exploration (api_list, api_list_tags, api_help), API invocation (api_call), command execution (exec), and file upload (upload). No overlapping functionality.
All tool names use lowercase with underscores where needed (api_call, api_list, api_list_tags, api_help, exec, upload). The pattern is predictable: API tools prefixed with 'api_', and standalone verbs for other actions.
With 6 tools, the server covers essential operations for Plesk management: API discovery, API calls, shell commands, and file uploads. The count is well-scoped, not excessive or sparse.
The tool surface covers API interaction and server operations thoroughly. A minor gap is the lack of a download tool, but exec can be used to retrieve files, so agents can work around it.