Ployz

Name: Ployz
Author: getployz

by getployzversion 1.0.0i★ –iRuns in the cloud

Registry namedev.ployz/ployz

Install

Overview

Description from the maker (original English)

Deploy apps, databases and previews to your own servers. Run Ployz Cloud from your agent.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://ployz.dev/mcp

Run this in your terminal

claude mcp add --transport http ployz https://ployz.dev/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ployz": {
      "url": "https://ployz.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ployz": {
      "type": "http",
      "url": "https://ployz.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://ployz.dev/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain ployz.dev (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

More stars than 0% of the other 1384 servers in this category
Published to the registry more recently than 68% of the other 1384 servers in this category
Basic checks equal to or better than 100% of the other 1384 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ployz safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 22 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Ployz

Rent a server. Get a cloud.

Preview environments on servers you own. One command from a fresh server to https.

Website · Quick start · Agents · Status · Self-host

Ployz 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.

The workflow of the hosted platforms you like, on servers you rent.

Six hosted platforms. Ployz isn't affiliated with any of 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

   ployz login

From your app's directory, point Ployz at your server.

   ployz up --server root@your-server

Ployz 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 up names the service after your app's directory, here shop. The preview copies a postgres service 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. Paid Ployz Cloud plans are coming soon. Your hosting provider bills you for the servers.

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

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

What's different

Use it with your agent

Quick start

How it works

Status

Pricing

Self-hosting the dashboard

How Ployz is built

Contributing

License