Ploi MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`token`	No	Ploi API token (passed as a command-line argument --token or -t)
`PLOI_API_TOKEN`	No	Ploi API token from ploi.io/profile/api-keys

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
list_serversB	List all servers in your Ploi account
get_serverC	Get details of a specific server
restart_serverC	Restart a server
get_server_logsD	Get server logs
list_sitesC	List all sites on a server
get_siteC	Get details of a specific site
deploy_siteB	Trigger deployment for a site and wait for it to complete. Returns status when done.
get_site_logsC	Get deployment/site logs
suspend_siteC	Suspend a site
resume_siteC	Resume a suspended site
deploy_projectA	Deploy the current project using .ploi.json config file and wait for completion. Use this when the user says 'deploy' without specifying a site.
get_project_deploy_statusC	Check deployment status for the current project using .ploi.json config
find_site_by_domainB	Search for a site by domain name across all servers
init_projectA	Initialize .ploi.json config for a project by searching for a domain. Use when user wants to link a project to a Ploi site.
list_databasesC	List databases on a server
create_database_backupC	Create a backup of a database

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

Latest Blog Posts

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sudanese/ploi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server