Server providing Argo CD integration for MCP clients.
Nothing to run from here
Plesk Deploy is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
75/100
trust score
9
tools declared
local
runs on your machine
—
downloads a day
What it does
Safe, approval-gated Plesk deployments: inspect, generate and validate a kit; status, logs, rollback
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user plesk-deploy-mcp '--' npx -y plesk-deploy-mcp
# 2 — ask your agent for something these tools do
# deploy_logs, deploy_status, generate_deploy_kit and 6 more
Plesk Deploy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 1 server
usama-saeed8311 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Plesk Deploy as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user plesk-deploy-mcp '--' npx -y plesk-deploy-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take PLESK_DEPLOY_SSH_HOSTS (Comma-separated ~/.ssh/config host aliases the SSH tools may reach. Unset: the SSH tools are off.), PLESK_DEPLOY_GITHUB_TOKEN (Optional read-only fine-grained token (Actions: read) for github_deploy_runs on private repositories.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Returns the last lines of the release manager’s deploy log on the server, through sudo -n <app>-deploy --log <lines> over the user’s own ssh (a host alias allowed in PLESK_DEPLOY_SSH_HOSTS). It goes through the deploy account’s single sudo rule, because the log is root-only. Values that look…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_alias | yes | — | |
| app | yes | — | |
| lines | integer | no | How many lines from the end |
Runs <app>-deploy --status on the server over the user’s own ssh (a host alias allowed in PLESK_DEPLOY_SSH_HOSTS) and returns the releases, newest first, with their commits, which one is live, and which failed. Read-only; needs no sudo. Use it to see what is deployed, before a rollback (to show…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_alias | yes | — | |
| app | yes | — |
Renders the deploy kit for a project from explicit parameters: .github/workflows/deploy-plesk.yml and deploy/plesk/ (build-bundle.sh, the <app>-deploy release manager, deploy.conf.example, server-setup.sh, the database dump helper, PM2 or systemd definitions, optional nginx directives, README.md).…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_dir | no | — | |
| app | yes | — | |
| stack | string | yes | Which build-bundle.sh branch builds the release |
| process_manager | string | yes | What the server reloads after the switch; keep what runs today |
| branch | no | The production branch | |
| ci_workflow | no | The existing CI workflow the deploy calls for its tests | |
| site_url | yes | The public site, checked from outside after each deploy | |
| public_health_url | yes | — | |
| base_dir | yes | BASE on the server: where releases/, current and shared/ live | |
| health_checks | array | yes | — |
| health_commit_url | no | A URL whose answer must contain the release’s commit | |
| app_user | no | The account that runs the app, from the server. Left as FILL IN if unknown | |
| app_group | no | — | |
| deploy_user | no | The SSH account GitHub Actions uses (default <app>-deploy) | |
| node_bin_dir | no | The folder with the node (and pm2) the app uses, e.g. /opt/plesk/node/24/bin | |
| pm2_home | no | — | |
| pm2_apps | array | no | Each PM2 process: its name, its folder in the release, its script, and arguments |
| systemd_units | array | no | — |
| php_fpm_service | no | The domain's FPM service, e.g. plesk-php83-fpm | |
| php_version | string | no | — |
Reads the recent runs of the "Deploy to Plesk" workflow from the GitHub API: status, conclusion, commit, branch, link, whether a run is waiting for approval in the production environment, and its jobs. Read-only: it never approves, re-runs or cancels anything. For a private repository it uses the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | yes | — | |
| workflow | no | — | |
| branch | no | — | |
| limit | integer | no | — |
| include_jobs | boolean | no | — |
Reads a project folder on this machine (manifests, lockfiles, runtime pins, framework configs, Dockerfiles, CI workflows, migrations, source code) and returns a Deployment facts table, each fact marked verified (with the file it came from) or unknown. Also lists the deployable apps with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_dir | no | — |
DESTRUCTIVE: makes the previous good release live again on the server by running sudo -n <app>-deploy --rollback over the user’s own ssh (a host alias allowed in PLESK_DEPLOY_SSH_HOSTS). The release manager switches current back, reloads the processes and checks health. Migrations are NOT…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_alias | yes | — | |
| app | yes | — | |
| confirm | string | yes | Exactly "<app>@<host_alias>", typed after the user confirmed |
| timeout_seconds | integer | no | — |
Runs the fixed, read-only discovery commands (the same ones server_discovery_commands lists) on the Plesk server over the user’s own ssh, through a ~/.ssh/config host alias the user allowed in PLESK_DEPLOY_SSH_HOSTS. It can’t run any other command. Values that look like secrets are redacted from…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host_alias | yes | — | |
| sudo | boolean | no | Run the commands as root with sudo -n |
| sections | array | no | Only these sections |
Returns the block of read-only commands for the user to run as root on the Plesk server and paste back (phase 2): Plesk and OS, who runs the app (PM2 as root and as the domain user, systemd), listening ports and nginx directives, the document root, git status of the app folder, env file NAMES…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| app | no | — | |
| system_user | no | The domain's system user (Plesk subscription), if known | |
| pm2_processes | array | no | PM2 process names, if known |
| app_dir | no | The folder the app runs from today, if known | |
| env_file | no | The path of the app's current .env on the server, if known |
Checks the deploy kit in a project (deploy/plesk/ and .github/workflows/deploy-plesk.yml) without touching anything outside a temporary folder. It runs bash -n on every script, shellcheck if installed, a YAML parse of the workflows, and checks of the workflow’s safety settings…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_dir | no | — | |
| app | no | The app name, if deploy/plesk holds more than one *-deploy script | |
| run_release_manager_tests | boolean | no | Run the release manager suite (about 20 seconds) |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Plesk Deploy or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
CTrust score 75 / 100
Release 0.1.0 · scanned 7 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score85
Client score75
Findings2 threat · 5 capability
Capabilitycritical
Coveragesource
Verificationsource
Surface digesta1d141e84e40967de558d22e895558184c6e9deac5a75fcfae0e52f93c32fbdb
Score vectorthreat 85 → client 75
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | critical | capability blast radius (critical) — client exposure if the model is manipulated | −10 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (9 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. critical is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| deploy_logs | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| deploy_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| generate_deploy_kit | sensitive-sourcestate-write | sensitive-source: keyword "dump"; state-write: declares readOnlyHint: false, destructiveHint: true |
| github_deploy_runs | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| inspect_project | no tags | |
| rollback | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| server_discover | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| server_discovery_commands | no tags | |
| validate_deploy_kit | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
deploy_logs → generate_deploy_kit → rollback
A cross-tool exfiltration chain exists: deploy_logs → generate_deploy_kit → rollback.
Supply chain and provenance
Integrityfirst-seen
Surface digesta1d141e84e40967d
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Plesk Deploy can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.