Skip to main content
Glama

Related Servers

Alternatives to opsgate

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Local zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.
      4
      55 PyPI
      5
      Apache 2.0
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to call backend tools under per-agent policy, deciding which tools each agent can see, what arguments it may pass, how often it may call, and which writes wait for human approval. It also redacts secrets and PII from tool results, fences untrusted output against injection, and records every call in a hash-chained audit log.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents policy-checked tools for shell commands, file reads and writes, HTTP fetches and tool calls, deciding each action against a policy before it runs while tracking secret taint and recording every decision in a tamper-evident audit log.
      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
      A
      quality
      B
      maintenance
      Enables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.
      12
      15 npm
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (docker_start/stop/restart, service_start/stop/restart/reload, nginx_test/reload). A couple of pairs overlap, notably journal_errors vs journal_tail (the former is just a filtered convenience view) and service_status's embedded log lines vs journal_tail, but descriptions mostly disambiguate.

    Naming Consistency4/5

    Strong resource_action pattern throughout (docker_*, service_*, file_*, journal_*, nginx_*), so an agent can predict names. Minor deviations: compose_ps uses 'ps' like docker_ps while systemd uses service_list, and a few tools (disk_usage, listening_ports, system_info) are descriptive rather than verb-form.

    Tool Count4/5

    25 tools is at the heavy end but spread across seven genuine domains (Docker, Compose, systemd, nginx, files, journal, network/system), so each tool earns its place. It sits just above the comfortable 3-15 band but the breadth justifies it.

    Completeness4/5

    Covers the core lifecycle for containers and services (list/status/start/stop/restart/reload/inspect/logs/stats) plus diagnostics and config validation for nginx. Gaps are minor and largely intentional (no file write, no docker exec, no compose up/down), which an agent can work around via service/file tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues