Ployz
Overview
Description from the maker (original English)
Deploy apps, databases and previews to your own servers. Run Ployz Cloud from your agent.
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: Databases & datasets
Install
Pick the AI app you use, then copy the settings.
Passed 4/5 checks · What you ask goes through the maker’s server (ployz.dev)
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1
Open Claude’s Connectors page
CustomizeConnectors
Click “+ Add” → “Add custom connector” and fill in these 2 fields
Copy each value into the field with the same name in Claude, then click Continue
Name · NamePloyzRemote MCP server URL · Addresshttps://ployz.dev/mcpLeave Authentication as Claude detected it, then click Add
Turn it on in a chat
+ConnectorsPloyz
Try it
Use Ployz and tell me what you can do for me, then show me one thing✓ If Claude says it is using Ployz or shows a Ployz tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT on business plans only
ChatGPT Business, Enterprise or Edu on the web, added by a workspace admin or owner · On Free, Plus or Pro: your ChatGPT plan cannot connect MCP yet
Open ChatGPT’s add-MCP page on the web
Plugins+Add custom MCP server
Fill in the name and address
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Name · NamePloyzConnection · Addresshttps://ployz.dev/mcpPick Ployz in a chat
Start a new chat and pick Ployz from your plugins before typing
Try it
Use Ployz and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Ployz or shows a Ployz tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --transport http ployz https://ployz.dev/mcpType /mcp in Claude Code
You should see Ployz listed as connected
Try it
Use Ployz and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Ployz or shows a Ployz tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Open the AI chat in Cursor in Agent mode
Try it
Use Ployz and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Ployz or shows a Ployz tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Open the AI chat in VS Code in Agent mode
Try it
Use Ployz and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Ployz or shows a Ployz tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://ployz.dev/mcpJSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Over the web
Claude Code
claude mcp add --transport http ployz https://ployz.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ployz": {
"url": "https://ployz.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"ployz": {
"type": "http",
"url": "https://ployz.dev/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Related guides
What it can do
The server asks you to sign in before it lists its tools.
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 12, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain ployz.dev (the registry checks domain ownership)
- ✓ Pass
Still maintained
Code last changed yesterday
- ! Caution
Has a licence
GitHub could not identify the licence type; open the file to check
- ✓ Pass
Endpoint responds
Responded in 1067 ms (HTTP 401)
- ✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Databases & datasetsi
- More stars than 92% of the other 1170 servers in this category
- Published to the registry more recently than 63% of the other 1170 servers in this category
- Basic checks equal to or better than 51% of the other 1170 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 4 of 5 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 yesterday, and the latest version (1.0.0) reached the registry 28 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 Business and above.
What can I use instead?
In the same category: Dbx, MCP Toolbox for Databases, MCP Toolbox for Databases
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
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.mdIt 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 Appployz 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.