Skip to main content
Glama
mariuszbyahoo

ops-copilot-mcp

by mariuszbyahoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ops-copilot-mcp

No user-submitted related servers found.

    Related Servers

    • Combined MCP Server

      SMH01-MOD-NEXT
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that gives AI agents controlled access to a machine: filesystem, shell, background processes, git, web fetching and persistent key-value memory.
      GPL 3.0

    • gov-mcp

      liuhaotian2024-prog
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.
      MIT

    • agent-receipts

      yulinlina
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides append-only, tamper-evident local receipts for AI agent actions, capturing command executions, outputs, and handoff evidence.
      MIT

    • dockhand

      Theo-Gkisis
      F
      license
      B
      quality
      B
      maintenance
      An MCP server that gives LLMs direct control over a local Docker daemon, enabling container, image, volume, network, and Compose stack management through natural language.
      23
      4
      -

    • approval-gate

      yulinlina
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides human-in-the-loop approval for risky AI agent actions, with durable state and audit logs.
      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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: ping for health, list_containers for inventory, get_container_logs for log retrieval, and restart_container for a mutating operation. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Tools use lowercase snake_case with a verb_noun pattern (list_containers, get_container_logs, restart_container). The exception is 'ping', which is a single verb but is a conventional health-check name and does not detract from overall consistency.

    Tool Count5/5

    Four tools form a well-scoped set for a Docker operations copilot, covering health, listing, logs, and restart. The count is appropriate for the narrow domain and each tool earns its place.

    Completeness4/5

    The core monitoring and restart workflow is covered, but there are minor gaps such as no explicit start/stop container controls. Agents can work around this given the focus on restart and diagnostics.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources