api_list_tags
List available Plesk API tags. Start here to explore Plesk APIs.
LABSCO SUMMARY
It manages the Plesk server itself, shell and file uploads included.
Beyond core administration over the Plesk and WP Toolkit REST APIs, it runs shell commands and uploads files on the server. It runs locally on your machine, several Plesk servers can be attached at once, and pairing it with a Plesk documentation MCP server gives the agent more accurate answers about Plesk usage.
What it is
An MCP server for administering Plesk servers from AI agents and apps, built on the Plesk REST API and the WP Toolkit REST API.
What you get
- Core Plesk server administration through the Plesk and WP Toolkit REST APIs.
- Shell commands run on the server, and file uploads to it.
Requirements
A Plesk server with API access enabled, its address, and an API key or an admin username and password. The uv Python package manager to run it.
Setup effort
One command plus a key — uvx plesk-mcp@latest, then supply credentials
USE CASES
01
Running a command on the Plesk server
Run a short shell command on the server, or upload a file first and use it in the next command. Subscriptions without shell access, or with a chrooted shell, refuse the command.
6 tools
Listed in project code.
api_list
List available Plesk APIs.
api_help
Explain how to call a specific Plesk API.
api_call
Call Plesk API. Do not use any preconceived notions about how to use Plesk API. Instead validate usage with api_help tool.
exec
Executes a command on the Plesk server and returns the result.
upload
Uploads a file with the given content to the Plesk server and returns the file path.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools registered in the project's code. The README doesn't list the tools. api_list_tags, api_list, api_help and api_call are a gateway to the Plesk REST API (and the WP Toolkit API when it is available): you look an operation up, then run it through api_call, so far more is reachable than the list suggests.
Requires
- uvx on PATH
- PLESK_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx plesk-mcp@latestMCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"plesk": {
"command": "uvx",
"args": [
"plesk-mcp@latest"
],
"env": {
"PLESK_HOST": "<YOUR_PLESK_URL>:8443",
"PLESK_API_KEY": "<YOUR_PLESK_API_KEY>"
}
}
}
}<YOUR_PLESK_URL>:8443 is the base URL of your own Plesk server (it may include the port). The all-zero PLESK_API_KEY is a sample: create a key on the server with plesk bin secret_key --create -description 'Plesk MCP'. Instead of the key you can set PLESK_USERNAME and PLESK_PASSWORD. If the server has no valid TLS certificate, the project's --insecure flag in args turns off the check, which it does not recommend.
Other MCP clients
OTHER MCP CLIENTS · JSON
{
"mcpServers": {
"plesk": {
"command": "uvx",
"args": [
"plesk-mcp@latest"
],
"env": {
"PLESK_HOST": "<YOUR_PLESK_URL>:8443",
"PLESK_API_KEY": "<YOUR_PLESK_API_KEY>"
}
}
}
}<YOUR_PLESK_URL>:8443 is the base URL of your own Plesk server (it may include the port). The all-zero PLESK_API_KEY is a sample: create a key on the server with plesk bin secret_key --create -description 'Plesk MCP'. Instead of the key you can set PLESK_USERNAME and PLESK_PASSWORD. If the server has no valid TLS certificate, the project's --insecure flag in args turns off the check, which it does not recommend.
