Manage your Plesk hosting server using AI assistants.
Connect Runs on your machine
claude mcp add plesk-mcp -e PLESK_HOST=<PLESK_HOST> -e PLESK_API_KEY=<PLESK_API_KEY> -e PLESK_USERNAME=<PLESK_USERNAME> -e PLESK_PASSWORD=<PLESK_PASSWORD> -- uvx plesk-mcp==0.1.1
{
"mcpServers": {
"plesk-mcp": {
"command": "uvx",
"args": [
"plesk-mcp==0.1.1"
],
"env": {
"PLESK_HOST": "<PLESK_HOST>",
"PLESK_API_KEY": "<PLESK_API_KEY>",
"PLESK_USERNAME": "<PLESK_USERNAME>",
"PLESK_PASSWORD": "<PLESK_PASSWORD>"
}
}
}
}
{
"mcpServers": {
"plesk-mcp": {
"command": "uvx",
"args": [
"plesk-mcp==0.1.1"
],
"env": {
"PLESK_HOST": "<PLESK_HOST>",
"PLESK_API_KEY": "<PLESK_API_KEY>",
"PLESK_USERNAME": "<PLESK_USERNAME>",
"PLESK_PASSWORD": "<PLESK_PASSWORD>"
}
}
}
}
{
"servers": {
"plesk-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"plesk-mcp==0.1.1"
],
"env": {
"PLESK_HOST": "<PLESK_HOST>",
"PLESK_API_KEY": "<PLESK_API_KEY>",
"PLESK_USERNAME": "<PLESK_USERNAME>",
"PLESK_PASSWORD": "<PLESK_PASSWORD>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
PLESK_HOSTOptional | Base URL of your Plesk server. May include port. Example: https://plesk.example.com:8443 |
PLESK_API_KEYOptional | Plesk API key. Create via `plesk bin secret_key --create -description 'Plesk MCP'` on the server. Required, unless PLESK_USERNAME and PLESK_PASSWORD are provided. |
PLESK_USERNAMEOptional | Username for authenticating with your Plesk server. Typically "admin". |
PLESK_PASSWORDOptional | Password for authenticating with your Plesk server. |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 4 May 2026 |
| Last updated | 4 May 2026 |
| Registry name | io.github.FlayedOne/plesk-mcp |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
