Ployz MCP server
Commit 15 Nov 2026Mengubah Linux server menjadi platform deployment untuk menghosting aplikasi, database, dan preview environment dengan HTTPS otomatis serta private networking.
Juga dikenal sebagai getployz/ployz
- Stars
- 8
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 1.0.0
- Commit terakhir
- 15 Nov 2026
- Lisensi
- —
Apa itu Ployz MCP?
Ployz adalah MCP server. Mengubah Linux server menjadi platform deployment untuk menghosting aplikasi, database, dan preview environment dengan HTTPS otomatis serta private networking.
Ringkasan dibuat dari README proyek
Tentang Ployz MCP server
Ployz mengubah Linux server yang Anda sewa menjadi platform deployment cloud pribadi. Platform ini memungkinkan developer untuk menghosting aplikasi, database, dan background workers di hardware sendiri, sambil menyediakan HTTPS otomatis melalui Caddy dan private WireGuard network. Sistem ini dirancang untuk bekerja dengan Linux server apa pun yang dapat diakses via SSH sebagai root, menggunakan systemd dan Docker untuk mengelola service.
User berinteraksi dengan platform melalui CLI atau web dashboard. Tool ini sangat berguna untuk membuat preview environment yang terisolasi untuk setiap pull request, lengkap dengan instance database khusus. Karena engine dan dashboard bersifat open source, aplikasi Anda akan tetap berjalan meskipun layanan pusat Ployz Cloud tidak tersedia. Platform ini mendukung scaling service hingga 50 replika di berbagai server dalam private network Anda.
Apa yang bisa Anda lakukan dengannya
- 1Deploy via coding agentsIzinkan AI agent untuk mengelola deployment dan branch environment menggunakan MCP tools yang terdaftar.
- 2Scale services across serversJalankan beberapa replika dari sebuah service di seluruh private network dari mesin Linux milik Anda.
- 3Review deployment changesPeriksa diff dari perubahan infrastruktur yang diusulkan sebelum diterapkan ke produksi.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Ployz MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Ployz MCP di Claude Code
$ claude mcp add --transport http ployz https://ployz.dev/mcpInstal Ployz MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp"
}
}
}Instal Ployz MCP di VS Code
.vscode/mcp.json
{
"servers": {
"ployz": {
"type": "http",
"url": "https://ployz.dev/mcp"
}
}
}Instal Ployz MCP di VS Code CLI
$ code --add-mcp '{"name":"ployz","type":"http","url":"https://ployz.dev/mcp"}'Instal Ployz MCP di Codex
$ codex mcp add ployz --url https://ployz.dev/mcpInstal Ployz MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.ployz] url = "https://ployz.dev/mcp"
Instal Ployz MCP di Gemini CLI
$ gemini mcp add -s user --transport http ployz https://ployz.dev/mcpInstal Ployz MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp",
"type": "http"
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaugetployz/ployz is public and reachablegithub.com/getployz/ployz ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)No licenseTemuan
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-13github.com/getployz/ployz ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPHTTPS endpoint answered 401 (sign-in required)Lolos
README
Lihat di 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.
Pertanyaan tentang Ployz MCP
Bagaimana cara menambahkan Ployz MCP ke Claude Code?
Jalankan claude mcp add --transport http ployz https://ployz.dev/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Ployz MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bisakah saya memindahkan aplikasi produksi?
Bisa, asalkan Anda mengikuti production checklist, meskipun Anda bertanggung jawab atas update OS dan saat ini belum tersedia managed offsite backups serta automatic failover.
Bagaimana Ployz menangani networking antar server?
Server Anda berbagi private WireGuard network, yang memungkinkan layanan menjalankan replika di beberapa server sekaligus.
Apa yang terjadi jika Ployz Cloud down?
Aplikasi Anda akan tetap berjalan di server karena aplikasi bergantung pada engine lokal, bukan pada cloud dashboard.
Apakah Ployz mendukung Docker Compose?
Tidak, Anda harus menambahkan setiap container sebagai service individu.