Skip to main content
Glama
herlonventura

vhe-deploy-mcp

by herlonventura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vhe-deploy-mcp

No user-submitted related servers found.

    Related Servers

    • WebsiteOps MCP Server

      anilreddykota
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges AI coding assistants with website codebases, local git repositories, and shared hosting via FTP/SFTP, enabling code discovery, file management, git operations, smart deployments, backups, and rollbacks.
      3 npm
      MIT

    • krexel-mcp

      Syfer-web
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to deploy, manage, and rollback websites via the Krexel API, supporting site uploads, deploys, logs, rollbacks, environment variables, and status checks.
      9
      46 npm
      MIT

    • Plugins-O2Switch

      mrll-lucas
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage O2Switch hosting accounts, including deploying sites, managing subdomains, SSL certificates, WordPress, email, cron jobs, and more, with human confirmation for sensitive actions.
      1
      MIT

    • cloud71 MCP connector

      7t1-studio
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to deploy generated files (HTML, PDF, images, etc.) directly to cloud71 hosting, returning a public URL, and manage cloud71 sites via natural language.
      MIT

    • ftp-mcp

      kemalabuteliyte
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to perform FTP/FTPS/SFTP file operations including upload, download, sync, and directory management with multi-server support.
      36
      26 npm
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action (listing, testing, comparing, previewing, backing up, deploying, registering) with no overlapping responsibilities. The descriptions clearly differentiate their purposes, preventing agent misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (list_sites, test_connection, compare_site, preview_deploy, backup_site, deploy_site, register_site). The naming is predictable and adheres to a single convention.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a deployment workflow. Each tool serves a clear function without redundancy, fitting comfortably within the ideal range for a domain-specific server.

    Completeness4/5

    The tools cover the core deployment lifecycle: registration, connection testing, comparison, preview, backup, and deployment. Minor gaps exist (e.g., no explicit update or delete site operation), but the essential workflow is fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources