# Ployz

Wires your coding agent into Ployz, which builds the app and runs its databases and pull-request previews on Linux servers you rent.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 7
- Author: getployz
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/getployz/ployz
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/ployz

## What it 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.

## Requirements
- Needs: Docker
- Remote server: `https://ployz.dev/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http ployz https://ployz.dev/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add ployz --url https://ployz.dev/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "ployz": {
            "url": "https://ployz.dev/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "ployz": {
            "type": "http",
            "url": "https://ployz.dev/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http ployz https://ployz.dev/mcp
```

## When to use it
- 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
- Set up Ployz on `root@your-server` and 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 `postgres` seeded via `pnpm db:seed`

## Similar
- [mirrord-prev-env](https://affpapa.org/en/nevibecode/skills/mirrord-prev-env.md) — skill · ★ 29
- [convex-self-heal](https://affpapa.org/en/nevibecode/skills/convex-self-heal.md) — skill · 36100 installs
- [Feedbacks](https://affpapa.org/en/nevibecode/mcp/feedbacks.md) — MCP server · ★ 36
- [ShareBox](https://affpapa.org/en/nevibecode/mcp/sharebox.md) — MCP server · ★ 30
- [artifact-site](https://affpapa.org/en/nevibecode/mcp/artifact-site.md) — MCP server · ★ 23
- [MCP Hangar](https://affpapa.org/en/nevibecode/mcp/mcp-hangar.md) — MCP server · ★ 18

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md