Skip to main content
Glama
GT-dinuo

server-ops-mcp

by GT-dinuo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to server-ops-mcp

No user-submitted related servers found.

    Related Servers

    • connect-to-server-mcp

      vstlmkh
      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
      35 npm
      MIT

    • ssh-pro-mcp

      a1113622001
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage remote servers via SSH, including command execution, multi-host batch operations, SFTP file transfer, background job handling, DevOps diagnostics, port tunneling, and safety guardrails like high-risk command blocking and read-only mode.
      MIT

    • DPLoy

      wellmb
      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

    • ssh-mcp-server

      ZachFlint
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely execute remote SSH commands, perform file transfers, and monitor system status through a standardized interface. It features robust security controls including command whitelisting, blacklisting, and credential isolation to prevent unauthorized operations.
      10
      8 npm
      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

    B3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (file, log, nginx, certbot, system), but there is potential confusion between command_exec and confirm_execute, as both handle confirmation for certain operations. Additionally, system_info overlaps partially with memory_analysis and disk_analysis, though they offer deeper analysis.

    Naming Consistency3/5

    Tool names consistently use snake_case and mostly follow an object_action pattern (e.g., file_read, log_search, nginx_reload). However, some actions are verbs (install, exec, delete) while others are nouns (analysis, overview, status, info), and 'confirm_execute' uses two verbs without a clear object, reducing consistency.

    Tool Count4/5

    With 23 tools, the set is on the higher end of the appropriate range but still well-scoped for server operations. Each tool has a specific purpose, and the count is justified by the breadth of tasks covered (files, logs, nginx, certbot, system analysis).

    Completeness4/5

    The tool set covers core server operations: file CRUD, logging, nginx configuration and reload, certbot installation and renewal, and system analysis. Minor gaps exist, such as no certbot revocation, no tool for restarting services beyond nginx, and no direct git deployment tools beyond status checking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources