Skip to main content
Glama
plesk-deploy-mcp

plesk-deploy-mcp

Related Servers

Alternatives to plesk-deploy-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Plesk hosting environments through a set of standardized tools for security, health monitoring, DNS, email, backups, and service management.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to deploy applications and manage servers over SSH using natural language commands, with built-in tools for Python bots, Docker Compose, and SSL setup.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely inspect remote servers and execute only pre-defined SSH commands, with optional HTTP checks and human-approved one-time codes required for changes.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform zero-downtime SSH deployments, atomic rollbacks, health-checked auto-rollback, service restarts, log inspection, and audit logging through MCP tools.
      181 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to inspect and manage remote hosts over SSH with tiered blast-radius containment that classifies and blocks destructive commands, plus forensic post-flight assertions that verify ports, processes, files, and HTTP health. It also provides long-running background task envelopes and atomic SFTP file editing with automatic backups, unified diffs, and one-click rollback.
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to check repository deploy readiness, deploy apps to your own cloud (AWS, Google Cloud, Azure, DigitalOcean), and migrate apps from platforms like Heroku, Railway, Render, or Vercel with rollback.
      MIT

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct phase of the deploy lifecycle, and the descriptions explicitly sequence them (inspect → discover → generate → validate → status/logs/rollback). The only real confusion risk is server_discovery_commands vs server_discover, which share the same command set and are separated only by a "you can't reach the server yourself" distinction; deploy_status, deploy_logs and github_deploy_runs also overlap in purpose but differ clearly in data source.

    Naming Consistency3/5

    Most names are snake_case verb_noun (inspect_project, generate_deploy_kit, validate_deploy_kit, server_discover, github_deploy_runs), which is readable. But deploy_status and deploy_logs drop the verb entirely, rollback is a bare verb, and server_discovery_commands is a long noun phrase, so the pattern breaks down across roughly a third of the set.

    Tool Count5/5

    Nine tools is well within the sweet spot and each maps to a concrete, non-trivial step (inspect, discover, generate, validate, status, logs, rollback, CI runs). Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the full lifecycle from project inspection through discovery, kit generation, validation, rollback and CI monitoring, with read-only/write guards throughout. The notable gaps are that deploys are only observed via github_deploy_runs (no tool to trigger a deploy) and the descriptions repeatedly say to verify the live URL from outside, yet no health-check tool exists.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues