Skip to content
MCP server

Plesk Deploy

Approval-gated Plesk deploy kits with status, logs and rollback over your own SSH

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, self-hosted
Runs
Locally
Version
0.1.0
Listing updated
2 days ago

About Plesk Deploy

Plesk Deploy is an open-source MCP server for cloud and infrastructure. It runs locally on your machine and is started by your AI client.

The server covers a specific release flow: GitHub Actions tests a project and builds a bundle, a person approves it in the production environment, and a small release manager on the Plesk server unpacks it into a new folder, backs up the database, migrates, switches over atomically and checks health. If the new release is unhealthy, it rolls back by itself.

Locally the agent can inspect a project, render the whole deploy kit as a diff you review (a dry run unless write: true is passed), and validate it. With SSH tools enabled for named host aliases, it can read releases, deploy logs and run a rollback; there is no run-any-command tool, and rollback needs an exact confirmation string.

Secrets are kept out of the loop. No tool accepts or returns keys or tokens, env files are read for variable names only, results are scanned for secret-like text, and there is no telemetry. SSH tools stay off until PLESK_DEPLOY_SSH_HOSTS lists the aliases. It needs Node.js 22 or later and is not affiliated with Plesk or WebPros.

Install

Run in a terminal

claude mcp add plesk-deploy-mcp --env PLESK_DEPLOY_GITHUB_TOKEN='<PLESK_DEPLOY_GITHUB_TOKEN>' -- npx -y plesk-deploy-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "plesk-deploy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "plesk-deploy-mcp"
      ],
      "env": {
        "PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "plesk-deploy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "plesk-deploy-mcp"
      ],
      "env": {
        "PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "plesk-deploy-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "plesk-deploy-mcp"
      ],
      "env": {
        "PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "plesk-deploy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "plesk-deploy-mcp"
      ],
      "env": {
        "PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "plesk-deploy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "plesk-deploy-mcp"
      ],
      "env": {
        "PLESK_DEPLOY_GITHUB_TOKEN": "<PLESK_DEPLOY_GITHUB_TOKEN>"
      }
    }
  }
}

Configuration

  • PLESK_DEPLOY_SSH_HOSTSComma-separated ~/.ssh/config host aliases the SSH tools may reach. Unset: the SSH tools are off.
  • PLESK_DEPLOY_GITHUB_TOKENOptional read-only fine-grained token (Actions: read) for github_deploy_runs on private repositories.

Tools this server provides (9)

Taken from the project documentation; the running server may differ.

inspect_project
Returns a table of deployment facts for a project.
server_discovery_commands
Gives read-only commands for you to run on the server.
generate_deploy_kit
Renders the deploy kit, as a dry run unless write is true.
validate_deploy_kit
Checks the kit and runs the release manager's tests in a temporary folder.
server_discover
Runs the same read-only discovery commands over SSH.
deploy_status
Lists releases on the server and which one is live.
deploy_logs
Shows the end of the deploy log.
rollback
Makes the previous good release live; destructive and needs confirmation.
github_deploy_runs
Reports the status of recent Deploy to Plesk runs.

What it does

Deploy kit generation
Renders the deployment files as a reviewable diff, writing only when asked.
Kit validation
Checks the generated kit and runs the release manager's tests in a temporary folder.
Remote status and logs
Reads releases, the live one and the end of the deploy log over SSH.
Confirmed rollback
Makes the previous good release live after an exact host confirmation.
Host allowlist
SSH tools only reach aliases named in PLESK_DEPLOY_SSH_HOSTS and use strict host key checking.
GitHub run status
Reports recent Deploy to Plesk runs and whether one awaits approval.

Good for

  • Set up approval-gated deployments for a project on a Plesk server
  • Check which release is live and read the last deploy log
  • Roll back a bad release from the agent
  • See whether the last Deploy to Plesk workflow passed
  • Review generated deploy files before writing them

Pricing

Open source

Plesk Deploy FAQ

Can it deploy from my laptop?

No. Deploys run in GitHub Actions behind a production approval, and no tool builds, uploads or deploys.

Are the SSH tools on by default?

No. They stay off until you list host aliases in PLESK_DEPLOY_SSH_HOSTS.

Does it handle my secrets?

The README says no tool accepts or returns a key, password or token, and output is redacted.

What does it need?

Node.js 22 or later, except in Claude Desktop, which brings its own.

What protects rollback?

It requires an exact confirmation string naming the host and app, and is never interrupted halfway.

Is Plesk Deploy free?

Yes. Plesk Deploy is open source, so you can use and self-host it for free.

How do I add Plesk Deploy to Claude Code?

Run this command in your terminal: claude mcp add plesk-deploy-mcp --env PLESK_DEPLOY_GITHUB_TOKEN='<PLESK_DEPLOY_GITHUB_TOKEN>' -- npx -y plesk-deploy-mcp

What are the best alternatives to Plesk Deploy?

The closest alternatives to Plesk Deploy are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to Plesk Deploy

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools