Is io.github.zyno-io/zynohosting safe to use?

io.github.zyno-io/zynohosting has no known CVEs as of the latest MCPpedia security scan. It requires authentication to connect, which limits unauthorized access. Licensed under MIT.

How do I install io.github.zyno-io/zynohosting?

io.github.zyno-io/zynohosting supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.zyno-io/zynohosting do?

io.github.zyno-io/zynohosting provides 13 tools: ZYNO_HOSTING_API_KEY, ZYNO_HOSTING_TENANT_ID, ZYNO_HOSTING_API_URL, ZYNO_HOSTING_CONFIG, list_sites and 8 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.zyno-io/zynohosting?

io.github.zyno-io/zynohosting is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.

Is io.github.zyno-io/zynohosting actively maintained?

io.github.zyno-io/zynohosting is actively maintained - last commit was 2 days ago.

io.github.zyno-io/zynohosting

@zyno-io/zynohosting

Manage ZynoHosting sites and create, discover, embed, and configure ZynoForms through local stdio.

287/wk 13 tools GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 2d ago

Works with most clients

Transport: stdio, sse

13 tools · ~306 tok

Grade A · 0.2% of 200K ctx

MCPpedia last refreshed this data 19h ago

Edit this pageView history

io.github.zyno-io/zynohosting is an MCP server that manage ZynoHosting sites and create, discover, embed, and configure ZynoForms through local stdio. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 79/100 on MCPpedia's security, maintenance and efficiency rubric.

DevOps

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "zynohosting": {
      "env": {
        "ZYNO_HOSTING_MCP_ROOTS": "/absolute/path/to/project"
      },
      "args": [
        "-y",
        "@zyno-io/zynohosting",
        "mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-zyno-io-zynohosting)](https://mcppedia.org/s/io-github-zyno-io-zynohosting)

Read me

What io.github.zyno-io/zynohosting does

Manage ZynoHosting sites and create, discover, embed, and configure ZynoForms through local stdio.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.

npx -y '@zyno-io/zynohosting' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

79/100across 5 weighted dimensions

How we score →

0255075100

−21

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @zyno-io/zynohosting against OSV.dev.

Inventory

Tools (13)

Click any tool to inspect its schema.

~306 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.zyno-io/zynohosting safe to use?: io.github.zyno-io/zynohosting has no known CVEs as of the latest MCPpedia security scan. It requires authentication to connect, which limits unauthorized access. Licensed under MIT.
How do I install io.github.zyno-io/zynohosting?: io.github.zyno-io/zynohosting supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.zyno-io/zynohosting do?: io.github.zyno-io/zynohosting provides 13 tools: ZYNO_HOSTING_API_KEY, ZYNO_HOSTING_TENANT_ID, ZYNO_HOSTING_API_URL, ZYNO_HOSTING_CONFIG, list_sites and 8 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.zyno-io/zynohosting?: io.github.zyno-io/zynohosting is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is io.github.zyno-io/zynohosting actively maintained?: io.github.zyno-io/zynohosting is actively maintained - last commit was 2 days ago.

Similar servers

Others in devops

View all →

Mcp Gitlab96

MCP server for using the GitLab API

2.1k 12

io.github.zenml-io/mcp-zenml93

MCP server for discovering, reading, and changing ZenML resources with compact generic tools

49 17

io.github.dynatrace-oss/dynatrace-managed-mcp92

MCP server for Dynatrace Managed to access logs, events, and metrics.

34 2

Mcp Server Azure Devops91

An MCP server for Azure DevOps

400 33

MCP Security Weekly

Get CVE alerts and security updates for io.github.zyno-io/zynohosting and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

DevOps

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "zynohosting": {
      "env": {
        "ZYNO_HOSTING_MCP_ROOTS": "/absolute/path/to/project"
      },
      "args": [
        "-y",
        "@zyno-io/zynohosting",
        "mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-zyno-io-zynohosting)](https://mcppedia.org/s/io-github-zyno-io-zynohosting)

Read me

What io.github.zyno-io/zynohosting does

Manage ZynoHosting sites and create, discover, embed, and configure ZynoForms through local stdio.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.

npx -y '@zyno-io/zynohosting' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

ZynoHosting CLI and MCP server

@zyno-io/zynohosting is the public command-line and local MCP client for ZynoHosting. It can:

list sites authorized for the current tenant credential;
inspect, download, upload, and delete individual files;
plan and apply complete deployments to production or an isolated preview slot;
promote current preview content to production;
set a static site's missing-page handling (sites set --not-found single-page-application);
download a complete deployable snapshot or, with the extra permission, all user content;
discover, create, inspect, edit, embed, and configure published ZynoForms (JSON in, JSON out);
teach coding agents to drive the CLI through one skill file;
expose the same operations through a local stdio MCP server, packaged as a Claude desktop extension.

The package requires Node.js 24.

Full CLI and MCP documentation is available at cli.zyno.host.

Install

npm install --global @zyno-io/zynohosting
zynohosting --help

It installs two executables:

zynohosting — the command-line interface for people, coding agents, and CI;
zynohosting-mcp — the local stdio MCP server, mainly for the Claude desktop app.

You can also run commands without a global install:

npx -y @zyno-io/zynohosting sites list

Authenticate

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

Where no browser can open (SSH, a cloud computer, no display), login shows a link and a short code instead, which the person opens and approves on any device (--device forces it). Agents that only show output when a command exits use zynohosting login --device --no-wait --json, then zynohosting login --resume --json. The person chooses how long the access lasts: 1 hour, 1 day, 7 days or 30 days (--lifetime only suggests one). A cloud computer with no system credential store can add --credential-store file.

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.

Logins are saved per environment, so signing in to alpha never replaces the production login. Production is the default; pass --environment alpha (or set ZYNOHOSTING_ENVIRONMENT) to use another saved login. Each environment keeps one login per account and tenant (signing in again as the same account in the same tenant replaces that login; another account or tenant adds one): zynohosting logins lists them, zynohosting logins use <tenant> changes the default, and --tenant <name|id> (or ZYNOHOSTING_TENANT) picks one for a single command. Revoke the active login and remove its local credentials with zynohosting logout, one named login with --tenant, or every saved login with zynohosting logout --all.

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. The Hosting API URL comes from --api-url, --environment, ZYNOHOSTING_API_URL, ZYNOHOSTING_ENVIRONMENT, then production, and the saved login is the one for that URL. Credentials are resolved in this order:

command options;
environment variables;
the saved login file.

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

79/100across 5 weighted dimensions

How we score →

0255075100

−21

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @zyno-io/zynohosting against OSV.dev.

Inventory

Tools (13)

Click any tool to inspect its schema.

~306 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.zyno-io/zynohosting safe to use?: io.github.zyno-io/zynohosting has no known CVEs as of the latest MCPpedia security scan. It requires authentication to connect, which limits unauthorized access. Licensed under MIT.
How do I install io.github.zyno-io/zynohosting?: io.github.zyno-io/zynohosting supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.zyno-io/zynohosting do?: io.github.zyno-io/zynohosting provides 13 tools: ZYNO_HOSTING_API_KEY, ZYNO_HOSTING_TENANT_ID, ZYNO_HOSTING_API_URL, ZYNO_HOSTING_CONFIG, list_sites and 8 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.zyno-io/zynohosting?: io.github.zyno-io/zynohosting is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is io.github.zyno-io/zynohosting actively maintained?: io.github.zyno-io/zynohosting is actively maintained - last commit was 2 days ago.