World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage ZynoHosting sites and create, discover, embed, and configure ZynoForms through local stdio.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install ZynoHosting. Follow https://mcp.popnx.com/i/zyno-io-zynohosting.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ZynoHosting for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "zynohosting": { "command": "npx", "args": [ "-y", "@zyno-io/zynohosting", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ZynoHosting tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"zynohosting": {
"command": "npx",
"args": [
"-y",
"@zyno-io/zynohosting",
"mcp"
]
}
}
}Use ZynoHosting and tell me what you can do for me, then show me one thing✓ If Claude says it is using ZynoHosting or shows a ZynoHosting tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
ZYNOHOSTING_MCP_ROOTS Optional allowlist of absolute local roots for local-file MCP tools, separated by the platform path delimiter. Omit to allow any local path accessible to the MCP process.ZYNOHOSTING_API_KEY Optional tenant API key. Omit it when using credentials saved by zynohosting login.ZYNO_SUITE_API_URL Optional ZynoSuite API URL override for form tools. Standard production, alpha, and dev environments are inferred automatically.ZYNO_AUTH_API_URL Optional ZynoAuth API URL override for scoped-token renewal. Standard production, alpha, and dev environments are inferred automatically.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect ZynoHosting yet
ZynoHosting runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect ZynoHosting
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ZynoHosting for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user zynohosting -- npx -y @zyno-io/zynohosting mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ZynoHosting tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user zynohosting -- npx -y @zyno-io/zynohosting mcpYou should see ZynoHosting listed as connected
Use ZynoHosting and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using ZynoHosting or shows a ZynoHosting tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
ZYNOHOSTING_MCP_ROOTS Optional allowlist of absolute local roots for local-file MCP tools, separated by the platform path delimiter. Omit to allow any local path accessible to the MCP process.ZYNOHOSTING_API_KEY Optional tenant API key. Omit it when using credentials saved by zynohosting login.ZYNO_SUITE_API_URL Optional ZynoSuite API URL override for form tools. Standard production, alpha, and dev environments are inferred automatically.ZYNO_AUTH_API_URL Optional ZynoAuth API URL override for scoped-token renewal. Standard production, alpha, and dev environments are inferred automatically.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ZynoHosting for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "zynohosting": { "command": "npx", "args": [ "-y", "@zyno-io/zynohosting", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ZynoHosting tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use ZynoHosting and tell me what you can do for me, then show me one thing✓ If Cursor says it is using ZynoHosting or shows a ZynoHosting tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
ZYNOHOSTING_MCP_ROOTS Optional allowlist of absolute local roots for local-file MCP tools, separated by the platform path delimiter. Omit to allow any local path accessible to the MCP process.ZYNOHOSTING_API_KEY Optional tenant API key. Omit it when using credentials saved by zynohosting login.ZYNO_SUITE_API_URL Optional ZynoSuite API URL override for form tools. Standard production, alpha, and dev environments are inferred automatically.ZYNO_AUTH_API_URL Optional ZynoAuth API URL override for scoped-token renewal. Standard production, alpha, and dev environments are inferred automatically.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ZynoHosting for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "zynohosting": { "type": "stdio", "command": "npx", "args": [ "-y", "@zyno-io/zynohosting", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ZynoHosting tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use ZynoHosting and tell me what you can do for me, then show me one thing✓ If VS Code says it is using ZynoHosting or shows a ZynoHosting tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
ZYNOHOSTING_MCP_ROOTS Optional allowlist of absolute local roots for local-file MCP tools, separated by the platform path delimiter. Omit to allow any local path accessible to the MCP process.ZYNOHOSTING_API_KEY Optional tenant API key. Omit it when using credentials saved by zynohosting login.ZYNO_SUITE_API_URL Optional ZynoSuite API URL override for form tools. Standard production, alpha, and dev environments are inferred automatically.ZYNO_AUTH_API_URL Optional ZynoAuth API URL override for scoped-token renewal. Standard production, alpha, and dev environments are inferred automatically.Descriptions are as written by the maker.
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.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user zynohosting -- npx -y @zyno-io/zynohosting mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"zynohosting": {
"command": "npx",
"args": [
"-y",
"@zyno-io/zynohosting",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"zynohosting": {
"command": "npx",
"args": [
"-y",
"@zyno-io/zynohosting",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"zynohosting": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@zyno-io/zynohosting",
"mcp"
]
}
}
}ZYNOHOSTING_MCP_ROOTS envZYNOHOSTING_API_KEY secret envZYNO_SUITE_API_URL envZYNO_AUTH_API_URL envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 18, 2026
The registry name was verified with the GitHub account zyno-io, which owns the repo
Code last changed today
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/zyno-io-zynohosting)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.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed today, and the latest version (0.7.0) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one ZynoHosting | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
@zyno-io/zynohosting is the public command-line and local MCP client for ZynoHosting. It can:
The package requires Node.js 24.
Full CLI and MCP documentation is available at zyno-io.github.io/zynohosting-cli.
npm install --global @zyno-io/zynohosting
zynohosting --help
It installs two executables:
zynohosting — the human and CI command-line interface;zynohosting-mcp — the local stdio MCP server.You can also run commands without a global install:
npx -y @zyno-io/zynohosting sites list
For an interactive user:
zynohosting login --permission hosting.sitesRead
zynohosting login \ --name "Claude MCP — work laptop" \ --permission hosting.sitesRead \ --permission hosting.deploy \ --permission forms.create \ --permission forms.edit \ --renewable
Browser login creates a tenant-bound scoped CLI token. hosting.sitesRead is requested when no --permission is supplied; repeat the option to request the narrowest complete set for your workflow. Access tokens always expire after 60 minutes. --renewable stores the rotating renewal credential in the operating system credential store and lets long-running CLI/MCP processes refresh automatically. While MCP remains alive, it renews in the background even when no tools are being called; each request also checks freshness as a backstop. The renewal secret is never written to the JSON config file.
Revoke the saved scoped grant and remove its local credentials with zynohosting logout.
For CI or another non-interactive environment, inject a tenant API key:
export ZYNOHOSTING_API_KEY='...'
The CLI also accepts --environment production|alpha|dev and --api-url. Credentials are resolved in this order:
Relevant environment variables are:
ZYNOHOSTING_API_KEYZYNOHOSTING_ACCESS_TOKENZYNOHOSTING_TENANT_IDZYNOHOSTING_TOKEN_EXPIRES_ATZYNOHOSTING_API_URLZYNO_SUITE_API_URLZYNO_AUTH_API_URLZYNOHOSTING_ENVIRONMENTZYNOHOSTING_CONFIGZYNOHOSTING_LOGIN_URLzynohosting sites list
zynohosting sites get example.com zynohosting sites get 11111111-1111-4111-8111-111111111111 --json
A site may be addressed by its UUID, primary hostname, vanity hostname, or authorized alias.
Remote paths are relative to the site document root. Absolute paths, .., control characters, backslashes, and symbolic-link traversal are rejected.
zynohosting files list example.com
zynohosting files list example.com wp-content/themes --recursive
zynohosting files get example.com index.html --output ./index.html zynohosting files put example.com ./index.html index.html zynohosting files rm example.com obsolete.html --yes
Use ETags to prevent overwriting a file that changed since it was inspected:
zynohosting files put example.com ./index.html index.html --etag '"etag-from-list"'
zynohosting files rm example.com obsolete.html --etag '"etag-from-list"' --yes
Use --create to require that an uploaded path does not already exist.
zynohosting deploy example.com ./dist
zynohosting deploy example.com ./dist --dry-run zynohosting deploy example.com ./dist --yes
Deployment is always planned before it is applied. The client and node agent:
The mandatory deployment scope excludes platform-managed configuration, uploads, caches, logs, VCS data, and dependencies. Add project exclusions in .zynohostingignore or with --ignore.
An empty local deployment requires --allow-empty before it may delete the remote deployable scope.
The default snapshot mirrors the deployable scope:
zynohosting download example.com ./site-copy
Downloading protected configuration and user-generated content requires the separate hosting.downloadSensitive permission:
zynohosting download example.com ./complete-copy --sensitive
The destination must be new or empty. Archive bytes are extracted as the hosting node generates them; the CLI validates the transport completion, gzip stream, and tar entries before atomically installing the staged tree. Absolute paths, traversal, links, devices, and other unsupported entries are rejected.
The MCP server is local stdio only. It does not open a port or provide a hosted/cloud MCP endpoint.
For a non-technical user, paste this into Codex or Claude Code:
Set up ZynoHosting MCP for this project if it's not already configured. See https://raw.githubusercontent.com/zyno-io/zynohosting-cli/main/docs/mcp/agent.md for details.
The agent configures only its own project file—.mcp.json for Claude Code or .codex/config.toml for Codex—without storing credentials. Restart the agent after it completes; MCP tools are not added to an already-running session. That prompt points at install instructions written for the agent; the matching prompts for the user cover signing in, publishing, and forms.
ZYNOHOSTING_MCP_ROOTS is an optional local-computer allowlist for the MCP process. When it is unset, local-file tools can use any absolute path the MCP process user can access. When roots are configured, local file reads, writes, deploy sources, ignore files, and download destinations are constrained to them after canonical path resolution.
Direct invocation:
zynohosting-mcp --root /absolute/path/to/project
The package’s main binary also exposes the registry-friendly form:
npx -y @zyno-io/zynohosting mcp --root /absolute/path/to/project
Example client configuration:
{
"mcpServers": { "zynohosting": { "command": "npx", "args": ["-y", "@zyno-io/zynohosting", "mcp"], "env": { "ZYNOHOSTING_MCP_ROOTS": "/absolute/path/to/project" } } } }
On macOS and Linux, multiple ZYNOHOSTING_MCP_ROOTS use : as the delimiter. Windows uses ;. Repeated --root arguments are also supported.
The MCP tools are:
loginlist_sitesget_sitelist_formsget_form_integrationdescribe_formcreate_basic_formupdate_formupdate_form_bot_protectionupdate_form_originslist_filesget_fileput_filedelete_fileplan_deployapply_deployplan_downloadapply_downloadFull deploys and downloads intentionally use separate plan/apply calls. Plans are held only in the local MCP process, contain no exposed bearer token, expire with their short-lived access session, and cannot be applied after the server restarts.
The MCP can start without a saved login. The agent calls login to open the ZynoSuite browser sign-in flow and receives the one-time URL in its tool result; after the browser callback, it calls login with action: "status" to confirm the login. It must never infer a deployment domain from the project or select a similar authorized site; it asks when the project does not state the target domain. If the stated domain is unavailable in the current login context, it must not substitute another one and should offer login again to switch contexts.
The tenant credential is limited by explicit Hosting and Forms permissions:
| Permission | Capability |
|---|---|
hosting.sitesRead | List and inspect sites |
hosting.filesRead | List files and download individual files |
hosting.filesWrite | Create and replace individual files |
hosting.filesDelete | Delete individual files |
hosting.deploy | Plan and apply full deployments |
hosting.download | Download the deployable snapshot |
hosting.downloadSensitive | Include protected and user-generated content |
hosting.analyticsRead | Read hosting analytics |
hosting.analyticsManage | Change analytics configuration |
forms.create | Create and immediately publish a basic form |
forms.edit | Edit a form, its Cap protection, and allowed CORS origins |
The form discovery and integration tools use the same tenant credential against the ZynoSuite API. Adding origins from a hosting-site reference also requires hosting.sitesRead.
Tenant admins receive the normal administrative defaults. Non-admin credentials receive only the operations explicitly granted to them.
That table is the complete set. zynohosting login --help prints it, and the MCP login tool enumerates it in its schema, so an invented key such as hosting.sitesWrite is rejected locally—naming the closest valid key—before a browser opens. CLI-token requests cannot include msp.login, msp.impersonate, core.changePassword, or core.manageFingerprints. The browser also refuses unknown permissions and permissions the current user does not possess; it never partially grants a request.
Only one MCP browser flow runs at a time. Repeating login with the same request returns the same one-time URL ("reused": true); requesting different permissions cancels the in-flight flow and issues a new URL rather than handing back the earlier scope. action: "cancel" abandons a flow and closes its loopback listener.
Most CLI commands accept --json. Deploy emits newline-delimited progress, plan, and result events; list and file commands emit a single JSON document.
The public documentation site covers CLI commands, MCP tools, configuration, permissions, and safety. The manager and node-agent contract is documented in BACKEND_PLAN.md. Maintainer release setup and the tag-only mirror design are documented in RELEASING.md.