Ployz MCP server
Commit Nov 15, 2026Turns Linux servers into a deployment platform to host apps, databases, and preview environments with automated HTTPS and private networking.
Also known as getployz/ployz
- Stars
- 8
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Nov 15, 2026
- License
- —
What is Ployz MCP?
Ployz turns Linux servers into a deployment platform to host apps, databases, and preview environments with automated HTTPS and private networking.
Summary generated from the project's README
About Ployz MCP server
Ployz transforms rented Linux servers into a personal cloud deployment platform. It allows developers to host applications, databases, and background workers on their own hardware while providing automated HTTPS through Caddy and a private WireGuard network. The system is designed to work with any Linux server reachable via SSH as root, using systemd and Docker to manage services.
Users interact with the platform through a CLI or a web dashboard. The tool is particularly useful for creating isolated preview environments for every pull request, complete with dedicated database instances. Because the engine and dashboard are open source, your applications continue to run even if the central Ployz Cloud service is unavailable. The platform supports scaling services up to 50 replicas across multiple servers within your private network.
What you can do with it
- 1Deploy via coding agentsAllow an AI agent to manage deployments and environment branches using registered MCP tools.
- 2Scale services across serversRun multiple replicas of a service across a private network of owned Linux machines.
- 3Review deployment changesInspect a diff of proposed infrastructure changes before they are applied to production.
Written from the project's README. Every use case is checked against a quote from it.
How to install Ployz MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Ployz MCP in Claude Code
$ claude mcp add --transport http ployz https://ployz.dev/mcpInstall Ployz MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp"
}
}
}Install Ployz MCP in VS Code
.vscode/mcp.json
{
"servers": {
"ployz": {
"type": "http",
"url": "https://ployz.dev/mcp"
}
}
}Install Ployz MCP in VS Code CLI
$ code --add-mcp '{"name":"ployz","type":"http","url":"https://ployz.dev/mcp"}'Install Ployz MCP in Codex
$ codex mcp add ployz --url https://ployz.dev/mcpInstall Ployz MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.ployz] url = "https://ployz.dev/mcp"
Install Ployz MCP in Gemini CLI
$ gemini mcp add -s user --transport http ployz https://ployz.dev/mcpInstall Ployz MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablegetployz/ployz is public and reachablegithub.com/getployz/ployz ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-13github.com/getployz/ployz ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubPloyz turns Linux servers you rent into a deployment platform. It builds your app, gives it an https address and runs its databases and workers next to it. Every pull request can get its own environment. Start with one server and add more when you need them.
What's different
- An environment for every pull request. Each preview runs the pull request's code at its own https address. Copy the database service and the preview gets its own empty database, seeded by your setup command. A database you leave shared gives the preview production data. On merge, production gets the code and the preview's setting changes. The Ployz · ready to merge check lists those changes on the pull request first.
- Review before you deploy. Edits from the dashboard, the CLI or an agent wait as a draft. You read the diff, then deploy it.
- The CLI does what the dashboard does. Commands print JSON with
--json. A change that would delete a service, a volume or a domain stops until a person approves it. An agent can't approve it. - One private network across your servers. Add a server with
ployz server add. Your servers share a WireGuard network, and a service runs up to 50 replicas across them. A service with a volume runs on the server that holds its data, one replica by default. - Apps that outlive Ployz Cloud. Your apps keep running on your servers if Ployz Cloud is down or goes away. The engine and the dashboard are open source.
Use it with your agent
Paste this into your coding agent.
Set me up for Ployz: https://ployz.dev/agents.md
It installs the CLI and the Ployz skill, signs you in and registers the Ployz MCP tools. From then on it runs the same commands you would.
> Copy production with its own worker, deploy it there, then stage it back.
$ ployz env branch try-worker --copy worker # Made Branch shop/try-worker of production.
$ ployz deploy --env try-worker # 2 deployed · across 1 server
$ ployz env sync --env try-worker --to # Synced try-worker → shop/production.
The change waits in production for you to review and deploy.
Quick start
You need a Linux server with systemd that you can reach as root over SSH. See the server requirements.
-
Install the CLI.
curl -fsSL https://ployz.sh | sh -
Sign in to Ployz Cloud.
ployz login -
From your app's directory, point Ployz at your server.
ployz up --server root@your-serverPloyz installs itself on the server, builds your app and prints its https address.
-
Deploy on every push, and give each pull request a preview with its own seeded database.
ployz github connect # install the Ployz GitHub App ployz set shop.repository=you/shop # build from GitHub instead of uploads ployz deploy ployz env pr you/shop --on --from production --copy postgres --setup 'shop=pnpm db:seed'ployz upnames the service after your app's directory, hereshop. The preview copies apostgresservice you've added.
How it works
Each server runs a small Ployz daemon next to Docker. Your servers share a WireGuard network and
keep each other up to date. Every server serves https itself through Caddy, so there's no load
balancer to rent. The dashboard and the CLI tell your servers what to run. Once deployed, your
apps depend on neither. Generated ployz.app addresses use Ployz's DNS. A custom domain with an
A record pointing at your servers doesn't.
Status
Can I move a production app? Yes, if the gaps below are fine for you. If you need managed backups and automatic failover today, wait. Ployz is young and changes quickly. Work through the production checklist first.
- You look after the OS. Ployz doesn't install OS updates.
- No offsite backups yet. Volume mirrors keep a copy on another server. Dump your databases on a schedule and keep the dumps off your servers, or keep your hosted database.
- No automatic failover. If a server dies, what ran only there stops. Replicas on other servers keep running.
- No Docker Compose files. Add each container as its own service.
- Alerts are email only. Ployz Cloud emails you when a service goes down or crashes.
Soon: offsite backups, automatic rollbacks, and moving a database to a bigger server without downtime.
Pricing
Ployz is free on your own servers, custom domains included. Your hosting provider bills you for the servers.
Mark your cluster as production on Ployz Cloud when you depend on it. That is $10 a month with two servers included, then $5 for each extra server. Nothing is locked today. Production pays for what doesn't run on your own servers, starting with longer log and metrics history.
Self-hosting the dashboard
Run the dashboard yourself instead of Ployz Cloud. See dashboard/README.md.
How Ployz is built
Agents write most of Ployz. I design the loop they run in, and I answer for what comes out of it.
Every change ships as a small PR. The agent has to prove it by running Ployz the way you would, on real servers. If it can't show me that, it doesn't merge. Low-risk PRs merge once the checks pass. The orchestrator, networking and anything touching your data get a human review first.
When an agent gets something wrong, we turn the mistake into a lint rule or a test. Every mistake makes the system stricter, and that's the part I trust.
Contributing
Bug reports and feature requests go in GitHub Issues.
The repository holds two projects. core/ is the engine, CLI and daemon, in Rust. dashboard/ is Ployz Cloud, in TypeScript. Each README explains how to build it.
License
The engine in core/ is Apache-2.0. The dashboard in dashboard/ is AGPL-3.0.
Ployz MCP questions
How do I add Ployz MCP to Claude Code?
Run claude mcp add --transport http ployz https://ployz.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Ployz MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can I move a production app?
Yes, provided you follow the production checklist, though you are responsible for OS updates and currently lack managed offsite backups and automatic failover.
How does Ployz handle networking between servers?
Your servers share a private WireGuard network, allowing services to run replicas across multiple servers.
What happens if Ployz Cloud goes down?
Your applications will continue to run on your servers because they depend on the local engine rather than the cloud dashboard.
Does Ployz support Docker Compose?
No, you must add each container as its own individual service.