Safe, approval-gated Plesk deployments: inspect, generate and validate a kit; status, logs, rollback
Connect Runs on your machine
claude mcp add plesk-deploy-mcp -e PLESK_DEPLOY_SSH_HOSTS=<PLESK_DEPLOY_SSH_HOSTS> -e PLESK_DEPLOY_GITHUB_TOKEN=<PLESK_DEPLOY_GITHUB_TOKEN> -- npx -y [email protected]
{
"mcpServers": {
"plesk-deploy-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PLESK_DEPLOY_SSH_HOSTS": "<PLESK_DEPLOY_SSH_HOSTS>",
"PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
}
}
}
}
{
"mcpServers": {
"plesk-deploy-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PLESK_DEPLOY_SSH_HOSTS": "<PLESK_DEPLOY_SSH_HOSTS>",
"PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
}
}
}
}
{
"servers": {
"plesk-deploy-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PLESK_DEPLOY_SSH_HOSTS": "<PLESK_DEPLOY_SSH_HOSTS>",
"PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
}
}
}
}
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_DEPLOY_SSH_HOSTSOptional | Comma-separated ~/.ssh/config host aliases the SSH tools may reach. Unset: the SSH tools are off. |
PLESK_DEPLOY_GITHUB_TOKENOptional, secret | Optional read-only fine-grained token (Actions: read) for github_deploy_runs on private repositories. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 6 Nov 2026 |
| Last updated | 6 Nov 2026 |
| Registry name | io.github.usama-saeed831/plesk-deploy-mcp |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
