Skip to main content
Glama

Ploi MCP Server

An MCP (Model Context Protocol) server that exposes Ploi.io API functionality as tools for AI assistants like Claude.

Deploy your sites with a simple "deploy" command - no clicking around in dashboards!

Features

  • One-command deployments - Just say "deploy" and watch it happen

  • Verified deploys - Deployments wait for real completion and report success/failure (no false "success")

  • Project linking - Link projects to Ploi sites with .ploi.json

  • Full site lifecycle - Create, delete, deploy, suspend, resume, view logs

  • Server management - List, restart, view logs

  • Environment & deploy script - Read and update a site's .env and deploy script without SSH

  • Daemons & queue workers - Manage queue:work daemons and Ploi's per-site queue workers (create/restart/pause/delete)

  • Cron jobs - Add/verify the Laravel scheduler (* * * * * schedule:run) and other crons

  • SSL certificates - Request (Let's Encrypt), list, and delete certificates

  • Databases - Create/delete databases; list, run, schedule, and delete backups

  • Service restart - Restart nginx / php-fpm / mysql / redis / supervisor

  • Optional id allowlist - Hard-bound which servers/sites the mutating tools may touch (see Configuration)

Related MCP server: Dokploy MCP Server

Installation

npm install -g ploi-mcp

Option 2: No Install (using npx)

Skip installation - npx will download and run it automatically when configured.

Quick Start

Step 1: Get your API token

Get your token from ploi.io/profile/api-keys.

🔐 Keep your token out of the command line. Passing --token exposes it in the process list (ps aux) and shell history, and stores it in plaintext in ~/.claude.json. Prefer one of the secure options below. ploi-mcp resolves the token in this order: --token-file → --token (deprecated) → PLOI_API_TOKEN env → ~/.ploi/config.php (the official ploi token store).

Step 2: Configure Claude Code

Add to ~/.claude.json — pass the token via the env block, not args:

If you installed globally:

{
  "mcpServers": {
    "ploi": {
      "type": "stdio",
      "command": "ploi-mcp",
      "env": { "PLOI_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}

If using npx (no install):

{
  "mcpServers": {
    "ploi": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "ploi-mcp"],
      "env": { "PLOI_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}

Already use the Ploi CLI? Run ploi token once and ploi-mcp will read the token from ~/.ploi/config.php automatically — no token in your MCP config at all.

Step 3: Restart Claude Code

Close and reopen Claude Code for the MCP server to load.

In Claude Code, say:

"Link this project to mydomain.com"

Step 5: Deploy anytime

Just say:

"deploy"

That's it! The deployment will run and notify you when complete.

Configuration

Claude Code

Add to ~/.claude.json:

{
  "mcpServers": {
    "ploi": {
      "type": "stdio",
      "command": "ploi-mcp",
      "args": ["--token", "YOUR_TOKEN"]
    }
  }
}

Or using environment variable:

{
  "mcpServers": {
    "ploi": {
      "type": "stdio",
      "command": "ploi-mcp",
      "env": {
        "PLOI_API_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

Claude Desktop

Add to config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "ploi": {
      "command": "ploi-mcp",
      "args": ["--token", "YOUR_TOKEN"]
    }
  }
}

The Ploi API token is account-wide — by default the assistant can deploy, restart, suspend, or delete-backups on any server or site in your account. Two layers reduce that blast radius:

  1. Scope the token itself. Create a least-privilege API token in Ploi (https://ploi.io/profile/api-keys) limited to only the servers you want the assistant to manage. This is the strongest bound — the MCP can't exceed what the token allows.

  2. Set an id allowlist (optional, defence-in-depth). When these env vars are set, every mutating tool (deploy_site, deploy_project, restart_server, suspend_site, resume_site, create/run/delete_database_backup) refuses ids outside the list. Read-only tools (list/get) are unaffected.

    {
      "mcpServers": {
        "ploi": {
          "command": "ploi-mcp",
          "env": {
            "PLOI_API_TOKEN": "YOUR_TOKEN",
            "PLOI_ALLOWED_SERVER_IDS": "12,34",
            "PLOI_ALLOWED_SITE_IDS": "567,890"
          }
        }
      }
    }

    Comma-separated ids. Unset or blank = no restriction (default). A typo (a non-numeric id) fails loudly rather than silently denying everything.

Usage

Command Line Options

ploi-mcp --token YOUR_TOKEN
ploi-mcp -t YOUR_TOKEN
PLOI_API_TOKEN=YOUR_TOKEN ploi-mcp

Project Setup

Link a project to its Ploi site for one-command deployments:

"Link this project to mydomain.com"

This creates .ploi.json in your project:

{
  "server_id": 12345,
  "site_id": 67890
}

Now just say "deploy" and it will:

  1. Trigger deployment

  2. Wait for completion (polling every 5 seconds)

  3. Report success or failure

Available Tools

Project Tools

Tool

Description

deploy_project

Deploy current project and wait for completion

init_project

Link project to a Ploi site by domain

get_project_deploy_status

Check deployment status

Server Management

Tool

Description

list_servers

List all servers

get_server

Get server details

restart_server

Restart a server

get_server_logs

Get server logs (auth, error, lastlog, syslog)

Site Management

Tool

Description

list_sites

List sites on a server

get_site

Get site details

find_site_by_domain

Search for a site by domain

create_site

Create a new site (vhost, directory, system user)

delete_site

Permanently delete a site (vhost, files, system user)

deploy_site

Deploy a site and wait for completion

get_site_logs

Get deployment logs

suspend_site

Suspend a site

resume_site

Resume a suspended site

Environment & Deploy Script

Tool

Description

get_site_env

Read a site's .env

update_site_env

Replace a site's .env (full-file)

get_deploy_script

Read a site's deploy script

update_deploy_script

Replace a site's deploy script (full-file)

Daemons

Tool

Description

list_daemons

List daemons (e.g. queue:work) on a server

create_daemon

Create a daemon

restart_daemon

Restart a daemon

toggle_daemon

Pause / resume a daemon

delete_daemon

Delete a daemon

Cron Jobs

Tool

Description

list_crons

List cron jobs on a server

create_cron

Create a cron job (e.g. the Laravel scheduler)

delete_cron

Delete a cron job

Queue Workers

Tool

Description

list_queues

List a site's queue workers

get_queue

Get a single queue worker

create_queue

Create a queue worker

restart_queue

Restart a queue worker

toggle_queue

Pause / resume a queue worker

delete_queue

Delete a queue worker

SSL Certificates

Tool

Description

list_certificates

List a site's certificates

request_certificate

Request a certificate (defaults to Let's Encrypt)

delete_certificate

Delete a certificate

Services

Tool

Description

restart_service

Restart nginx / php-fpm / mysql / redis / supervisor

Database Management

Tool

Description

list_databases

List databases on a server

create_database

Create a database (optionally with a user/password)

delete_database

Permanently delete a database

list_database_backups

List database backup configurations

get_database_backup

Get a database backup configuration

run_database_backup

Run an existing backup configuration now ("backup now")

create_database_backup

Create a scheduled backup configuration (needs a backup destination)

delete_database_backup

Delete a backup configuration

Note: mutating tools (anything that creates, updates, deletes, deploys, restarts, or toggles) carry a destructiveHint so MCP hosts can prompt before running them, and honour the optional id allowlist. update_site_env / update_deploy_script writes are applied asynchronously by Ploi — allow a few seconds before reading them back.

Example Commands

"List my servers"
"Deploy"
"Deploy mydomain.com"
"Create a Laravel site for app.mydomain.com"
"Add the scheduler cron to server 12"
"Restart the queue worker on app.mydomain.com"
"Request a Let's Encrypt cert for app.mydomain.com"
"Show me the .env for app.mydomain.com"
"Restart nginx on server 12"
"List my database backups"
"Run database backup 42 now"

Development

git clone https://github.com/sudanese/ploi-mcp.git
cd ploi-mcp
npm install
npm run build
npm link

License

MIT

Available Tools

46 tools
create_cronB
Destructive

Create a cron job on a server, e.g. the Laravel scheduler 'php /path/artisan schedule:run' at frequency '* * * * *'.

Inputs: server_id (required), command (required), frequency (required), user.

create_daemonA
Destructive

Create a daemon (long-running process) on a server, e.g. 'php artisan queue:work'.

Inputs: server_id (required), command (required), system_user (required), processes (required), +1 more.

create_databaseA
Destructive

Create a new database on a server (optionally with a dedicated user/password — Ploi auto-generates both when omitted).

Inputs: server_id (required), name (required), user, password.

create_database_backupA
Destructive

Create a SCHEDULED database backup configuration. Requires a pre-existing backup destination (backup_configuration id — see Ploi 'backup configurations'). This schedules backups; use run_database_backup to trigger one immediately.

Inputs: server_id (required), database_id (required), backup_configuration (required), interval (required), +1 more.

create_queueA
Destructive

Create a queue worker on a site (Ploi's first-class queue feature). Defaults: connection 'database', queue 'default', max-time 60s, sleep 30s, 1 process, 1 try.

Inputs: server_id (required), site_id (required), connection, queue, +4 more.

create_siteA
Destructive

Create a new site on a server (vhost, directory, system user). Provisions an empty site; install a repository/deploy separately.

Inputs: server_id (required), root_domain (required), web_directory, system_user, +1 more.

delete_certificateB
Destructive

Delete an SSL certificate from a site

Inputs: server_id (required), site_id (required), certificate_id (required).

delete_cronC
Destructive

Delete a cron job

Inputs: server_id (required), cron_id (required).

delete_daemonC
Destructive

Delete a daemon

Inputs: server_id (required), daemon_id (required).

delete_databaseA
Destructive

DELETE a database permanently. Irreversible — verify the database_id with list_databases first.

Inputs: server_id (required), database_id (required).

delete_database_backupB
Destructive

Delete a database backup configuration

Inputs: backup_id (required).

delete_queueB
Destructive

Delete a queue worker

Inputs: server_id (required), site_id (required), queue_id (required).

delete_siteA
Destructive

DELETE a site permanently — removes its nginx vhost, files, and system user. Irreversible. Double-check the site_id with get_site first.

Inputs: server_id (required), site_id (required).

deploy_projectA
Destructive

Deploy the current project using .ploi.json config file and wait for completion. Use this when the user says 'deploy' without specifying a site.

Inputs: project_path (required).

deploy_siteA
Destructive

Trigger deployment for a site and wait for it to complete. Returns status when done.

Inputs: server_id (required), site_id (required).

find_site_by_domainA
Read-only

Search for a site by domain name across all servers

Inputs: domain (required).

get_database_backupA
Read-only

Get a database backup configuration by id

Inputs: backup_id (required).

get_deploy_scriptA
Read-only

Read a site's deploy script (the shell commands Ploi runs on each deploy).

Inputs: server_id (required), site_id (required).

get_project_deploy_statusA
Read-only

Check deployment status for the current project using .ploi.json config

Inputs: project_path (required).

get_queueB
Read-only

Get a single queue worker by id

Inputs: server_id (required), site_id (required), queue_id (required).

get_serverA
Read-only

Get details of a specific server

Inputs: server_id (required).

get_server_logsB
Read-only

Get recent server activity logs

Inputs: server_id (required).

get_siteB
Read-only

Get details of a specific site

Inputs: server_id (required), site_id (required).

get_site_envA
Read-only

Read a site's .env file (APP_KEY, DB_*, queue/mail/Sentry config, etc.)

Inputs: server_id (required), site_id (required).

get_site_logsC
Read-only

Get deployment/site logs

Inputs: server_id (required), site_id (required).

init_projectA
Destructive

Initialize .ploi.json config for a project by searching for a domain. Use when user wants to link a project to a Ploi site.

Inputs: project_path (required), domain (required), overwrite.

list_certificatesA
Read-only

List the SSL certificates on a site

Inputs: server_id (required), site_id (required).

list_cronsA
Read-only

List the cron jobs (crontab entries) on a server

Inputs: server_id (required).

list_daemonsA
Read-only

List the daemons (long-running processes like queue:work) on a server

Inputs: server_id (required).

list_database_backupsA
Read-only

List database backup configurations (across the account)

Inputs: no named parameters.

list_databasesB
Read-only

List databases on a server

Inputs: server_id (required).

list_queuesA
Read-only

List the queue workers on a site

Inputs: server_id (required), site_id (required).

list_serversA
Read-only

List all servers in your Ploi account

Inputs: no named parameters.

list_sitesB
Read-only

List all sites on a server

Inputs: server_id (required).

request_certificateA
Destructive

Request an SSL certificate for a site (defaults to Let's Encrypt). Provisioning is async — check list_certificates for status.

Inputs: server_id (required), site_id (required), domains (required), type, +1 more.

restart_daemonA
Destructive

Restart a daemon (e.g. to pick up new code after a deploy)

Inputs: server_id (required), daemon_id (required).

restart_queueA
Destructive

Restart a queue worker (e.g. to pick up new code after a deploy)

Inputs: server_id (required), site_id (required), queue_id (required).

restart_serverB
Destructive

Restart a server

Inputs: server_id (required).

restart_serviceA
Destructive

Restart a server service (nginx, php-fpm, mysql, redis, supervisor) to apply config changes.

Inputs: server_id (required), service (required).

resume_siteA
Destructive

Resume a suspended site

Inputs: server_id (required), site_id (required).

run_database_backupA
Destructive

Run an existing database backup configuration now ('backup now'). Use list_database_backups to find the backup id.

Inputs: backup_id (required).

suspend_siteC
Destructive

Suspend a site

Inputs: server_id (required), site_id (required).

toggle_daemonA
Destructive

Pause or unpause a daemon (single toggle — pauses if running, resumes if paused)

Inputs: server_id (required), daemon_id (required).

toggle_queueA
Destructive

Pause or unpause a queue worker (single toggle — pauses if running, resumes if paused)

Inputs: server_id (required), site_id (required), queue_id (required).

update_deploy_scriptA
Destructive

Replace a site's deploy script with the given content (full-file PATCH — send the complete script, not a diff). Read it first with get_deploy_script. Ploi applies the write asynchronously, so allow a few seconds before reading it back.

Inputs: server_id (required), site_id (required), deploy_script (required).

update_site_envA
Destructive

Replace a site's .env file with the given content (full-file PATCH — send the complete file, not a diff). Read it first with get_site_env. Ploi applies the write asynchronously, so allow a few seconds before reading it back (an immediate get_site_env may 404 or show stale content).

Inputs: server_id (required), site_id (required), content (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 46 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create_cron, list_servers, restart_queue). Even similar operations like deploy_project and deploy_site are clearly differentiated by scope. No overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using underscores (create_, delete_, get_, list_, etc.). No mixing of conventions or inconsistent verbs.

    Tool Count2/5

    46 tools is significantly higher than the recommended range. While the server covers many subdomains, the count feels excessive for an MCP server and likely includes operations that could be merged or omitted.

    Completeness4/5

    The tool set provides comprehensive CRUD and lifecycle coverage for servers, sites, databases, cron, daemons, queues, certificates, backups, and deployment workflows. Minor gaps exist (e.g., no update_site or update_database), but core user workflows are well-supported.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Dokploy deployments, including creating and deploying applications, managing databases, configuring domains with SSL, and monitoring application status through a standardized interface.
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to manage cloud infrastructure through natural language by providing a unified interface to the Dokploy platform. Supports Docker containers, applications, databases, domains, monitoring, and deployment operations through conversational commands.
      50 npm
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage SpinupWP infrastructure, including servers, WordPress sites, and SSH keys through the SpinupWP v1 JSON API. Users can perform actions like provisioning sites, purging caches, and restarting services via natural language commands.
      17
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables managing Ploi.io servers, sites, databases, and Docker containers through the Ploi API, supporting both local stdio and remote Cloudflare Worker deployments with multi-tenant authentication.
      32
      ISC