The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the ZynoHosting listing page.
@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.
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:
For an interactive user:
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:
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_URLA 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.
Use ETags to prevent overwriting a file that changed since it was inspected:
Use --create to require that an uploaded path does not already exist.
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:
Downloading protected configuration and user-generated content requires the separate hosting.downloadSensitive permission:
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:
The package’s main binary also exposes the registry-friendly form:
Example client configuration:
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.