Skip to main content
Glama

Plesk 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.

Related MCP server: cPanel MCP 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.

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

Available Tools

6 tools
api_callA

Call Plesk API. Do not use any preconceived notions about how to use Plesk API. Instead validate usage with api_help tool.

Inputs: name (required), params (required).

api_helpA
Read-onlyIdempotent

Explain how to call a specific Plesk API.

Inputs: name (required). Returns: result

api_listB
Read-onlyIdempotent

List available Plesk APIs.

Inputs: tags. Returns: result

api_list_tagsA
Read-onlyIdempotent

List available Plesk API tags. Start here to explore Plesk APIs.

Inputs: no named parameters. Returns: result

execA

Executes a command on the Plesk server and returns the result.

The command CWD is the home directory of the user (e.g. /root for root user, or /var/www/vhosts/example.com for a subscription user). This tool will reject long commands. Keep the total length of the command, stdin, and env vars under about 740 characters.

This tool will fail for subscriptions with no or chrooted shell access (chrootsh).

Inputs: command (required), subscription, stdin, env. Returns: object

uploadA

Uploads a file with the given content to the Plesk server and returns the file path.

The file will be uploaded to a temporary location returned by this tool and can be used in subsequent commands. The file is uploaded as 0600 psaadm:psaadm, so make sure to set proper permissions and ownership after moving it. For example, subscription files should typically have 0644 $user:psacln. Make sure to set both.

Inputs: content (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: API exploration (api_list, api_list_tags, api_help), API invocation (api_call), command execution (exec), and file upload (upload). No overlapping functionality.

    Naming Consistency5/5

    All tool names use lowercase with underscores where needed (api_call, api_list, api_list_tags, api_help, exec, upload). The pattern is predictable: API tools prefixed with 'api_', and standalone verbs for other actions.

    Tool Count5/5

    With 6 tools, the server covers essential operations for Plesk management: API discovery, API calls, shell commands, and file uploads. The count is well-scoped, not excessive or sparse.

    Completeness4/5

    The tool surface covers API interaction and server operations thoroughly. A minor gap is the lack of a download tool, but exec can be used to retrieve files, so agents can work around it.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Plesk hosting environments through a set of standardized tools for security, health monitoring, DNS, email, backups, and service management.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage WHM hosting accounts and server administration tasks including account management, server stats, updates, SSL, backups, and email through a secure API.
      13
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 50 tools to manage a CloudPanel VPS through AI assistants, covering sites, databases, Docker, server software, firewall, DNS, and one-shot deployments.
      21 npm
      4
      MIT