MCP

Ploi hosts an MCP server at https://ploi.io/api/mcp. Any MCP client that supports the streamable HTTP transport with OAuth can connect: add the URL to your client, then authenticate when the client connects — a browser window opens where you log in to Ploi and approve the connection.

In Claude Code, adding the server only registers it. Start claude, run /mcp, select the Ploi server and choose Authenticate to complete the OAuth flow.

In ChatGPT, add Ploi as a custom connector: open Settings → Connectors → Create, enter the MCP server URL with OAuth authentication, and sign in to Ploi when prompted. You can then enable Ploi from the Tools menu in any chat.

Alternatively, you can authenticate with a regular API token as a bearer token, using the same scopes as the REST API.

The MCP server exposes a curated set of tools mirroring the REST API. Read tools require the matching *-read scope, write tools the matching *-create scope. Tokens issued through the OAuth flow carry the mcp:use scope, which grants access to every tool.

Destructive delete operations are intentionally not available through MCP. Mutations such as deployments and restarts run asynchronously: they queue work on your server and return immediately.

Servers — list-servers, get-server, list-server-logs, list-server-services, restart-server-service, restart-server

Sites — list-sites, get-site, list-site-logs, get-site-env, update-site-env, get-nginx-config, update-nginx-config

Deployments — deploy-site, list-deployments, get-deployment-log, get-deploy-script, update-deploy-script

Databases — list-databases, create-database, list-database-users

Cronjobs — list-cronjobs, create-cronjob

Certificates — list-certificates, request-certificate

Daemons & queues — list-daemons, restart-daemon, list-site-queues, restart-site-queue

Firewall — list-firewall-rules, create-firewall-rule