
Mcp Plesk Lite
io.github.mohamedbenharizPublished by GitHub account mohamedbenharizv1.1.2Updated Oct 24, 2026
MCP server for Plesk: manage domains, DNS, mail, SSL, backups, databases and WordPress via AI.
Overview
A local MCP server that lets an AI assistant manage a Plesk hosting panel: domains, DNS, mail, SSL, backups, databases and WordPress.
- What you can do
- Manage domains and DNS records on a Plesk server through the assistant. Handle mail settings, SSL certificates and backups. Work with databases and WordPress installations hosted in Plesk. The manifest lists no individual tools, so the exact operations available are not documented here.
- When to use it
- Useful when you run sites on a Plesk hosting panel and want an assistant to carry out routine hosting administration, such as domain, DNS, mail, SSL, backup, database or WordPress tasks, without clicking through the panel.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package mcp-plesk-lite over stdio. Desktop only. The manifest declares no authentication, environment variables or headers, so how it reaches a Plesk server and which credentials it needs are not documented here.
Installation
In SourceWeft
- Open Mcp Plesk Lite in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.1.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.