MCP server de Ployz
Commit 15 nov 2026Convierte servidores Linux en una plataforma de despliegue para alojar aplicaciones, bases de datos y entornos de preview con HTTPS automatizado y redes privadas.
También conocido como getployz/ployz
- Stars
- 8
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 1.0.0
- Último commit
- 15 nov 2026
- Licencia
- —
¿Qué es Ployz MCP?
Ployz es un MCP server. Convierte servidores Linux en una plataforma de despliegue para alojar aplicaciones, bases de datos y entornos de preview con HTTPS automatizado y redes privadas.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Ployz
Ployz transforma servidores Linux alquilados en una plataforma personal de despliegue en la nube. Permite a los desarrolladores alojar aplicaciones, bases de datos y workers en segundo plano en su propio hardware, proporcionando HTTPS automatizado a través de Caddy y una red privada WireGuard. El sistema está diseñado para funcionar con cualquier servidor Linux accesible vía SSH como root, utilizando systemd y Docker para gestionar los servicios.
Los usuarios interactúan con la plataforma a través de una CLI o un dashboard web. La herramienta es especialmente útil para crear entornos de preview aislados para cada pull request, con instancias de bases de datos dedicadas. Debido a que tanto el motor como el dashboard son de código abierto, tus aplicaciones seguirán funcionando incluso si el servicio central de Ployz Cloud no está disponible. La plataforma permite escalar servicios hasta 50 réplicas a través de múltiples servidores dentro de tu red privada.
Qué puedes hacer con él
- 1Despliegue mediante agentes de códigoPermite que un agente de IA gestione despliegues y ramas de entorno utilizando herramientas MCP registradas.
- 2Escalar servicios entre servidoresEjecuta múltiples réplicas de un servicio a través de una red privada de máquinas Linux propias.
- 3Revisar cambios de despliegueInspecciona un diff de los cambios de infraestructura propuestos antes de que se apliquen a producción.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Ployz MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Ployz MCP en Claude Code
$ claude mcp add --transport http ployz https://ployz.dev/mcpInstalar Ployz MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp"
}
}
}Instalar Ployz MCP en VS Code
.vscode/mcp.json
{
"servers": {
"ployz": {
"type": "http",
"url": "https://ployz.dev/mcp"
}
}
}Instalar Ployz MCP en VS Code CLI
$ code --add-mcp '{"name":"ployz","type":"http","url":"https://ployz.dev/mcp"}'Instalar Ployz MCP en Codex
$ codex mcp add ployz --url https://ployz.dev/mcpInstalar Ployz MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.ployz] url = "https://ployz.dev/mcp"
Instalar Ployz MCP en Gemini CLI
$ gemini mcp add -s user --transport http ployz https://ployz.dev/mcpInstalar Ployz MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp",
"type": "http"
}
}
}Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblegetployz/ployz is public and reachablegithub.com/getployz/ployz ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)No licenseHallazgo
- Commit o lanzamiento en el último añoLast commit or release 2026-11-13github.com/getployz/ployz ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPHTTPS endpoint answered 401 (sign-in required)Aprobado
README
Ver en 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.
Preguntas sobre Ployz MCP
¿Cómo agrego Ployz MCP a Claude Code?
Ejecuta claude mcp add --transport http ployz https://ployz.dev/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Ployz MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Puedo migrar una aplicación de producción?
Sí, siempre que sigas la lista de verificación de producción, aunque tú eres responsable de las actualizaciones del SO y actualmente no cuenta con backups externos gestionados ni failover automático.
¿Cómo gestiona Ployz la red entre servidores?
Tus servidores comparten una red privada WireGuard, lo que permite ejecutar réplicas de servicios en múltiples servidores.
¿Qué pasa si Ployz Cloud se cae?
Tus aplicaciones seguirán funcionando en tus servidores porque dependen del motor local y no del dashboard en la nube.
¿Soporta Ployz Docker Compose?
No, debes añadir cada contenedor como un servicio individual.