Plesk MCP server
✓ VerifiedAllows administrators to manage Plesk hosting servers, execute shell commands, and upload files using AI agents.
Also known as FlayedOne/plesk-mcp
- Stars
- 6
- Tools
- —
- Downloads, 30 days
- 7,689
- Latest version
- 0.1.1
- Last commit
- May 17, 2026
- License
- MIT
What is Plesk MCP?
Plesk allows administrators to manage Plesk hosting servers, execute shell commands, and upload files using AI agents.
Summary generated from the project's README
About Plesk MCP server
Managing hosting environments through AI agents is possible with plesk-mcp, which allows administrators to control Plesk servers using natural language. The server runs locally on your machine to keep sensitive information within your own environment. It connects to your hosting via the Plesk REST API and WP Toolkit REST API, enabling core administration tasks, shell command execution, and file uploads.
To set up the server, you need the uv Python package manager and a valid Plesk host address. You can authenticate using a PLESK_API_KEY or by providing a PLESK_USERNAME and PLESK_PASSWORD. The tool works with any supported Linux or Windows operating system running Plesk, though it has been specifically tested on Plesk Obsidian 18.0.76. For users managing multiple environments, the configuration allows attaching several Plesk servers simultaneously to a single agent setup.
What you can do with it
- 1Execute server shell commandsAn administrator can ask an AI agent to run specific terminal commands directly on the Plesk host.
- 2Upload files to hostingDevelopers can instruct an AI to transfer files from their local environment to the Plesk server.
Written from the project's README. Every use case is checked against a quote from it.
How to install Plesk MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Plesk MCP in Claude Code
$ claude mcp add plesk-mcp -- uvx plesk-mcpInstall Plesk MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"plesk-mcp": {
"command": "uvx",
"args": [
"plesk-mcp"
]
}
}
}Install Plesk MCP in VS Code
.vscode/mcp.json
{
"servers": {
"plesk-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"plesk-mcp"
]
}
}
}Install Plesk MCP in VS Code CLI
$ code --add-mcp '{"name":"plesk-mcp","type":"stdio","command":"uvx","args":["plesk-mcp"]}'Install Plesk MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"plesk-mcp": {
"command": "uvx",
"args": [
"plesk-mcp"
]
}
}
}Install Plesk MCP in Codex
$ codex mcp add plesk-mcp -- uvx plesk-mcpInstall Plesk MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.plesk-mcp] command = "uvx" args = ["plesk-mcp"]
Install Plesk MCP in Gemini CLI
$ gemini mcp add -s user plesk-mcp uvx -- plesk-mcpInstall Plesk MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"plesk-mcp": {
"command": "uvx",
"args": [
"plesk-mcp"
]
}
}
}Configuration
OPENAI_API_KEYPLESK_API_KEYPlesk 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_HOSTBase URL of your Plesk server. May include port. Example: https://plesk.example.com:8443
PLESK_PASSWORDPassword for authenticating with your Plesk server.
PLESK_USERNAMEUsername for authenticating with your Plesk server. Typically "admin".
| Name | Description | |
|---|---|---|
| OPENAI_API_KEY | — | |
| PLESK_API_KEY | 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_HOST | Base URL of your Plesk server. May include port. Example: https://plesk.example.com:8443 | |
| PLESK_PASSWORD | Password for authenticating with your Plesk server. | |
| PLESK_USERNAME | Username for authenticating with your Plesk server. Typically "admin". |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableflayedone/plesk-mcp is public and reachablegithub.com/flayedone/plesk-mcp ↗Pass
- Package names this repository as its sourceplesk-mcp names flayedone/plesk-mcp as sourcepypi.org/project/plesk-mcp/ ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-05-17github.com/flayedone/plesk-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from plesk-mcpPass
- No critical advisory in the package or its dependencies66 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubPlesk MCP Server
This MCP server for Plesk allows administrators to manage their Plesk servers using various AI agents and apps. It builds on top of Plesk REST API and WP Toolkit REST API, and provides core administration capabilities, as well as ability to manage the server through shell commands and upload files to the server.
The MCP server runs locally on your machine, so important information doesn't leave your environment.
Plesk Requirements
The MCP server is expected to support any sufficiently recent Plesk version (there are no strict limitations) and any OS (Linux or Windows) that Plesk supports. However, it was tested only on Plesk Obsidian 18.0.76, so prefer using a supported Plesk version.
Obviously, API access must not be disabled on the server.
MCP Server Requirements
You will need uv Python package manager to run the server. Refer to the official documentation for installation instructions.
Usage
Configure the server in your VS Code mcp.json or equivalent (in other agents or apps) using a configuration like:
{
"servers": {
"plesk": {
"command": "uvx",
"args": [
"plesk-mcp@latest"
],
"env": {
// Base URL of your Plesk server. May include port.
// If you don't have a valid TLS certificate or want to use HTTP,
// add the --insecure flag to the args above.
// However, this is not recommended as you credentials may be leaked as a result.
"PLESK_HOST": "https://plesk.example.net:8443",
// API key (recommended).
// Create via `plesk bin secret_key --create -description 'Plesk MCP'` on the server.
"PLESK_API_KEY": "00000000-0000-0000-0000-000000000000",
// Alternatively, you can use username and password.
"PLESK_USERNAME": "admin",
"PLESK_PASSWORD": "passwd"
}
}
}
}
You may want to use env file (e.g. via "envFile" parameter) if your agent or app supports it. This will avoid putting credentials directly in the config file.
See uvx plesk-mcp@latest --help for details on available options and environment variables.
Recommended Usage
For better behavior, it's recommended to use this MCP server in combination with a documentation MCP server. Select either plesk-local-docs-mcp or plesk-remote-docs-mcp. This will allow the agent to get more accurate information about Plesk usage when needed.
You may also attach several Plesk servers at once if needed (e.g. for managing multiple servers).
Here's an example configuration:
{
"servers": {
"plesk-docs": {
"command": "uvx",
"args": [
"plesk-local-docs-mcp@latest"
],
"env": {
"OPENAI_API_KEY": "sk-..."
}
},
"plesk1": {
"command": "uvx",
"args": [
"plesk-mcp@latest"
],
"env": {
"PLESK_HOST": "https://plesk1.example.net:8443",
"PLESK_API_KEY": "00000000-0000-0000-0000-000000000000"
}
},
"plesk2": {
"command": "uvx",
"args": [
"plesk-mcp@latest"
],
"env": {
"PLESK_HOST": "https://plesk2.example.net",
"PLESK_USERNAME": "admin",
"PLESK_PASSWORD": "passwd"
}
}
}
}
Development
MCP server run command:
uv run plesk-mcp --log-level debug --insecure
Before commit:
uv run ruff format
uv run ruff check --fix
uv run mypy .
uv run pytest
Publish:
uv build --clear
uv publish
mcp-publisher login github
mcp-publisher publish
Testing
Using Plesk Docker Image
If you don't have a Plesk instance but want to test this MCP server, you may use Plesk Docker image instead:
docker run -d --rm --tmpfs /tmp --tmpfs /run --tmpfs /run/lock -v /sys/fs/cgroup:/sys/fs/cgroup --cgroupns host -p 80:80 -p 443:443 -p 8880:8880 -p 8443:8443 --name plesk plesk/plesk
The Docker image startup is not instant, so give it a minute or so before trying to connect.
And then configure the MCP server as:
{
"servers": {
"plesk": {
"command": "uvx",
"args": [
"plesk-mcp@latest",
"--insecure"
],
"env": {
"PLESK_HOST": "https://localhost:8443",
"PLESK_PASSWORD": "changeme1Q**"
}
}
}
}
Without Plesk Server (Demo Mode)
Alternatively, run in demo mode from sources (with mocked responses):
{
"servers": {
"plesk": {
"command": "uv",
"args": [
"run",
"plesk-mcp"
],
"env": {
"PLESK_HOST": "https://linux.demo.example.net",
"PLESK_API_KEY": "-"
}
}
}
}
Automated tests
Unit tests run with uv run pytest (in the project root and in each sub-project). Smoke tests that exercise real services are skipped by default and selected via -m smoke:
# Plesk MCP smoke tests (against a reachable Plesk instance, e.g. from the Docker image described above)
PLESK_HOST=https://localhost:8443 PLESK_PASSWORD='changeme1Q**' PLESK_INSECURE=1 \
uv run pytest -m smoke
Plesk MCP questions
How do I add Plesk MCP to Claude Code?
Run claude mcp add plesk-mcp -- uvx plesk-mcp in your terminal. Add --scope user to make it available in every project.
How do I add Plesk MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.