The MCP server runs locally on your machine, so important information doesn't leave your environment.
The MCP server runs locally on your machine, so important information doesn't leave your environment. The plesk mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.
The server ships on PyPI as plesk-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 5 environment variables: PLESK_HOST, PLESK_API_KEY, PLESK_USERNAME, PLESK_PASSWORD, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by flayedone; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Plesk MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"plesk": {
"command": "uvx",
"args": ["plesk-mcp"],
"env": {
"PLESK_HOST": "your-value",
"PLESK_API_KEY": "your-value",
"PLESK_USERNAME": "your-value",
"PLESK_PASSWORD": "your-value",
"OPENAI_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PLESK_HOST | Endpoint or connection string the server talks to. | Optional |
| PLESK_API_KEY | Credential the server authenticates with. | Yes |
| PLESK_USERNAME | Configuration value read at startup. | Optional |
| PLESK_PASSWORD | Configuration value read at startup. | Optional |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.