- Home
- MCP servers
- Ploi
Ploi
- javascript
0
GitHub Stars
javascript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"sudanese-ploi-mcp": {
"command": "ploi-mcp",
"args": [
"--token",
"YOUR_TOKEN"
],
"env": {
"PLOI_API_TOKEN": "YOUR_TOKEN"
}
}
}
}You can deploy and manage Ploi sites and infrastructure through a single-command MCP server that exposes Ploi.io API features to your AI assistant. This enables hands-free deployments, server and site control, and automated maintenance tasks directly from your workflow.
How to use
Interact with the MCP server using an MCP client to deploy sites, manage servers, and monitor deployments. You will authenticate with a token, configure your MCP client to point at the local MCP server, and then issue high-level commands such as deploy, link projects, list resources, and view logs. The server provides one-command deployments, auto-wait for completion, and project linking to connect your codebase to a Ploi site.
How to install
Prerequisites you need before installing:
- Node.js and npm installed on your machine
- Access to your Ploi API token
- A terminal or shell with network access
Option 1: Global Install (Recommended)
npm install -g ploi-mcp
Note: This installs the MCP server globally so you can run it from any location.
Option 2: No Install (using npx)
Run directly with npx without installing
Skip installation by using npx. The MCP server will be downloaded and run automatically when configured.
Configuration and usage notes
You must provide your API token to authenticate with Ploi. You can configure the MCP client to use either a direct token flag or an environment variable.
Configure Claude Code to load the MCP server. Choose one of the following configurations depending on whether you installed globally or will use npx.
Security and tokens
Treat your API token as a secret. Do not expose it in public code or logs. Use environment variables or secure vaults when possible.
Examples of common workflows
Link a project to a Ploi site, then issue a deploy command to start a one-command deployment. The MCP server will wait for the deployment to finish and report the result.
Available tools
deploy_project
Deploy the current project to its linked Ploi site and wait for deployment completion.
init_project
Link a project to a Ploi site by domain to enable one-command deployments.
get_project_deploy_status
Check the deployment status for the linked project.
list_servers
List all MCP servers available or configured.
get_server
Get detailed information about a specific server.
restart_server
Restart a server to apply changes or recover from issues.
get_server_logs
Retrieve server logs including auth, error, lastlog, and syslog.
list_sites
List all sites on a given server.
get_site
Get detailed information about a specific site.
deploy_site
Deploy a site and wait for completion.
get_site_logs
Get deployment logs for a site.
suspend_site
Suspend a site to stop activity without deleting it.
resume_site
Resume a suspended site.
find_site_by_domain
Search for a site by its domain.
list_databases
List databases on a server.
create_database_backup
Create a backup of a database on a server.