Plesk MCP

Name: Plesk MCP
Author: FlayedOne

by FlayedOneversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.FlayedOne/plesk-mcp

Install

Overview

Description from the maker (original English)

Manage your Plesk hosting server using AI assistants.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: PLESK_HOST, PLESK_API_KEY, PLESK_USERNAME, PLESK_PASSWORD

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "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"
      }
    }
  }
}

Run this in your terminal

claude mcp add plesk --env PLESK_HOST=your-value --env PLESK_API_KEY=your-value --env PLESK_USERNAME=your-value --env PLESK_PASSWORD=your-value -- uvx plesk-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "plesk": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "plesk-mcp"
      ],
      "env": {
        "PLESK_HOST": "your-value",
        "PLESK_API_KEY": "your-value",
        "PLESK_USERNAME": "your-value",
        "PLESK_PASSWORD": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

PLESK_HOST env
Base URL of your Plesk server. May include port. Example: https://plesk.example.com:8443
PLESK_API_KEY env
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_USERNAME env
Username for authenticating with your Plesk server. Typically "admin".
PLESK_PASSWORD env
Password for authenticating with your Plesk server.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account FlayedOne, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32433 servers in this category
Published to the registry more recently than 8% of the other 32433 servers in this category
Basic checks equal to or better than 100% of the other 32433 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Plesk MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Symantec Cloud DLP AIops

by AIops-tools

Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

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

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Symantec Cloud DLP AIops

README from the maker

Plesk MCP Server

Plesk Requirements

MCP Server Requirements

Usage

Recommended Usage

Development

Testing

Using Plesk Docker Image

Without Plesk Server (Demo Mode)

Automated tests