MCP server Ployz
Commit 15 de nov. de 2026Transforma servidores Linux em uma plataforma de deployment para hospedar apps, bancos de dados e ambientes de preview com HTTPS automatizado e rede privada.
Também conhecido como getployz/ployz
- Stars
- 8
- Ferramentas
- —
- Downloads, 30 dias
- —
- Versão mais recente
- 1.0.0
- Último commit
- 15 de nov. de 2026
- Licença
- —
O que é o MCP Ployz?
Transforma servidores Linux em uma plataforma de deployment para hospedar apps, bancos de dados e ambientes de preview com HTTPS automatizado e rede privada.
Resumo gerado a partir do README do projeto
Sobre o MCP server de Ployz
O Ployz transforma servidores Linux alugados em uma plataforma pessoal de deployment na nuvem. Ele permite que desenvolvedores hospedem aplicações, bancos de dados e background workers em seu próprio hardware, fornecendo HTTPS automatizado via Caddy e uma rede privada WireGuard. O sistema foi projetado para funcionar com qualquer servidor Linux acessível via SSH como root, utilizando systemd e Docker para gerenciar os serviços.
Os usuários interagem com a plataforma através de uma CLI ou um dashboard web. A ferramenta é particularmente útil para criar ambientes de preview isolados para cada pull request, com instâncias de banco de dados dedicadas. Como o engine e o dashboard são open source, suas aplicações continuam rodando mesmo se o serviço central do Ployz Cloud estiver indisponível. A plataforma suporta o escalonamento de serviços em até 50 réplicas entre múltiplos servidores dentro da sua rede privada.
O que você pode fazer com ele
- 1Deploy via coding agentsPermita que um agente de IA gerencie deployments e branches de ambiente usando ferramentas MCP registradas.
- 2Scale services across serversExecute múltiplas réplicas de um serviço através de uma rede privada de máquinas Linux próprias.
- 3Review deployment changesInspecione um diff das mudanças de infraestrutura propostas antes que elas sejam aplicadas em produção.
Escrito a partir do README do projeto. Cada caso de uso é verificado com uma citação dele.
Como instalar o MCP Ployz
Formatos verificados em 10 nov 2026Adicionar ao CursorAdicionar ao GooseInstalar o MCP Ployz no Claude Code
$ claude mcp add --transport http ployz https://ployz.dev/mcpInstalar o MCP Ployz no Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp"
}
}
}Instalar o MCP Ployz no VS Code
.vscode/mcp.json
{
"servers": {
"ployz": {
"type": "http",
"url": "https://ployz.dev/mcp"
}
}
}Instalar o MCP Ployz no VS Code CLI
$ code --add-mcp '{"name":"ployz","type":"http","url":"https://ployz.dev/mcp"}'Instalar o MCP Ployz no Codex
$ codex mcp add ployz --url https://ployz.dev/mcpInstalar o MCP Ployz no Codex config.toml
~/.codex/config.toml
[mcp_servers.ployz] url = "https://ployz.dev/mcp"
Instalar o MCP Ployz no Gemini CLI
$ gemini mcp add -s user --transport http ployz https://ployz.dev/mcpInstalar o MCP Ployz no Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp",
"type": "http"
}
}
}Verificações automatizadas
Executado em 14 de nov. de 2026Relatório completo →Ainda não verificado. Um servidor precisa de uma pontuação de 80, nenhum problema grave e dados suficientes para verificarmos. Como as verificações funcionam · O que corrigir para ganhar mais pontos
- Repositório de origem vinculado e acessívelgetployz/ployz is public and reachablegithub.com/getployz/ployz ↗Passou
- O pacote indica este repositório como sua origemNão verificado
- Proveniência da build (atestação Sigstore)Não verificado
- Licença de código aberto (OSI)No licenseProblema encontrado
- Commit ou release no último anoLast commit or release 2026-11-13github.com/getployz/ployz ↗Passou
- OpenSSF ScorecardNão verificado
- Nome do pacote não é próximo a um pacote popularNão verificado
- Nenhum aviso crítico no pacote ou em suas dependênciasNão verificado
- Sem instruções ocultas para o modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPassou
- Ferramentas destrutivas estão rotuladasNão verificado
- O endpoint remoto responde ao handshake do MCPHTTPS endpoint answered 401 (sign-in required)Passou
README
Ver no 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.
Perguntas sobre o MCP Ployz
Como adiciono o MCP Ployz ao Claude Code?
Execute claude mcp add --transport http ployz https://ployz.dev/mcp no seu terminal. Adicione --scope user para torná-lo disponível em todos os projetos.
Como adiciono o MCP Ployz ao Cursor?
Abra ~/.cursor/mcp.json e adicione o servidor em mcpServers, usando a configuração do Cursor mostrada na seção de instalação acima.
Posso mover um app de produção?
Sim, desde que você siga o checklist de produção, embora você seja responsável pelas atualizações do SO e atualmente não conte com backups offsite gerenciados ou failover automático.
Como o Ployz gerencia a rede entre os servidores?
Seus servidores compartilham uma rede privada WireGuard, permitindo que os serviços executem réplicas em múltiplos servidores.
O que acontece se o Ployz Cloud ficar fora do ar?
Suas aplicações continuarão rodando em seus servidores porque elas dependem do engine local, e não do dashboard na nuvem.
O Ployz suporta Docker Compose?
Não, você deve adicionar cada container como um serviço individual próprio.