Skip to main content
Glama
devops-deploy-guard-mcp-server

devops-deploy-guard-mcp-server

by awais2o

Related Servers

Alternatives to devops-deploy-guard-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect and safely operate a Linux VPS through typed DevOps tools governed by YAML allowlists, read-only defaults, dry-run plans, secret redaction, and tamper-evident auditing.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to run shell commands, spawn persistent background tasks, and read/write files inside isolated remote container sandboxes on a VPS. It also provides project workspace listing, task attach/kill controls, and a searchable knowledge graph for memory continuity across sessions.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables a cloud-hosted AI agent to execute shell commands, manage background jobs, and drive interactive persistent terminals on a remote Linux VPS with native root privileges over MCP and HTTPS — no SSH, tunnel, or local runtime required. It also provides bearer-key authentication, key revocation, and a LAN-restricted dashboard for sessions and audit logs.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Zero-Ops deploy of a private AI coding workspace to your own VPS, straight from your AI chat. Registers the user, recommends a VPS, and runs and monitors the full deployment.
      69
      MIT
    • A
      license
      A
      quality
      C
      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

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct operation: inspection, environment setup, deployment planning, execution, rollback, etc. There is no overlap; even the two planning tools are differentiated (dynamic vs Docker).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with imperative verbs (inspect, resume, rollback, analyze, generate, verify, etc.). No mixed conventions.

    Tool Count5/5

    20 tools cover the full DevOps deployment lifecycle without being excessive. Each tool serves a clear and necessary purpose within the domain.

    Completeness5/5

    The tool set covers inspection, provisioning, environment setup, deployment planning, execution, rollback, recovery, health checks, and cleanup. No obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues