Plesk

What is Plesk?

Plesk is an MCP server that allows administrators to manage their Plesk servers using AI agents and apps. It builds on the Plesk REST API and WP Toolkit REST API, providing core administration capabilities, shell command execution, and file uploads. The server runs locally on your machine, keeping sensitive data within your environment.

How to use Plesk?

Configure the server in your MCP client (e.g., VS Code mcp.json) using the uvx command with the package plesk-mcp@latest. Set environment variables for the Plesk host URL and authentication (API key or username/password). You may attach multiple Plesk servers and optionally combine this server with a documentation MCP server for better agent performance.

Key features of Plesk

• Manage Plesk servers via AI agents and apps.
• Core administration through Plesk REST API.
• Execute shell commands on the server.
• Upload files to the server.
• Runs locally for data privacy.
• Supports multiple Plesk servers simultaneously.

Use cases of Plesk

• Automate routine Plesk administration tasks using natural language.
• Manage several Plesk servers from a single AI interface.
• Test Plesk interactions safely with a Docker-based instance or demo mode.

FAQ from Plesk

What Plesk version and OS are required?

Any sufficiently recent Plesk version and any OS (Linux or Windows) that Plesk supports should work. The server was tested on Plesk Obsidian 18.0.76, so a supported Plesk version is recommended. API access must be enabled on the server.

What do I need to run the Plesk MCP server?

You need uv, the Python package manager. See the Astral documentation for installation instructions.

How can I authenticate with the Plesk server?

You can use an API key (recommended) or a username/password. For API keys, create one with plesk bin secret_key --create -description 'Plesk MCP' on the server. Set the corresponding environment variables (PLESK_API_KEY or PLESK_USERNAME/PLESK_PASSWORD).

Can I manage multiple Plesk servers at once?

Yes, you can configure multiple server entries in your MCP client, each with its own host and credentials, and manage them simultaneously.

How can I test the server without a real Plesk instance?

You can run a Plesk Docker image locally or use demo mode with mocked responses by setting PLESK_HOST and PLESK_API_KEY to a demo host and - respectively. Smoke tests against a real instance are available with uv run pytest -m smoke.