Ployz — Claude Code MCP server: deploy apps to your own servers
Wires your coding agent into Ployz, which builds the app and runs its databases and pull-request previews on Linux servers you rent.
claude mcp add --transport http ployz https://ployz.dev/mcpWhat Ployz does
On each host Ployz runs a daemon beside Docker. Caddy serves https from the server itself, and your machines join a WireGuard network so services can spread across them. The MCP endpoint gives the agent the same verbs the CLI has, from ployz deploy to ployz env.
Nothing goes live straight from the agent. Edits land as a draft you read as a diff, then deploy. Destructive moves on a service, volume or domain wait for a human to approve, and an agent cannot be that human.
You bring a Linux machine with systemd reachable as root over SSH. Ployz leaves OS updates to you. Offsite backups are not part of it yet, and a dead server takes down whatever ran only there. Compose files get no special handling either: each container becomes a service of its own.
The MCP tools need an account, so run ployz login after installing the CLI. Pasting the setup prompt that points at https://ployz.dev/agents.md into your agent gets the CLI, the skill and the MCP registration done in one go.
What it helps with
- spin up a separate preview per pull request with its own seeded database
- ship an app to a rented server and get an https address back
- read a diff of the agent's changes before pushing them live
- link several servers into one private network
- connect a GitHub repo so pushes deploy automatically
Example prompts for the agent
- Set up Ployz on
root@your-serverand tell me the app address - Copy production with its worker, deploy it to a branch, then sync it back
- Give this pull request a preview with a fresh
postgresseeded viapnpm db:seed
How to install Ployz
Platform CLI: remote server
claude mcp add --transport http ployz https://ployz.dev/mcpPlatform CLI: remote server
codex mcp add ployz --url https://ployz.dev/mcpConfig file
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp"
}
}
}Config file
{
"servers": {
"ployz": {
"type": "http",
"url": "https://ployz.dev/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http ployz https://ployz.dev/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Ployz
How do I install the Ployz MCP server in Claude Code?
Run claude mcp add --transport http ployz https://ployz.dev/mcp. Deploying also needs the CLI: curl -fsSL https://ployz.sh | sh, then ployz login.
What does Ployz do?
It builds your app, runs it with https on servers you own, and keeps databases and workers next to it. The MCP tools let an agent drive the same operations a person runs in the CLI.
Can I move a production app onto Ployz?
Yes, as long as the current gaps work for you — there are no offsite backups and no automatic failover. Walk the production checklist in the repo first, since the project changes fast.
