Skip to main content
Glama
skyvanguard

infra-ops-mcp

by skyvanguard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to infra-ops-mcp

No user-submitted related servers found.

    Related Servers

    • auto-om

      atoncooper
      A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive MCP server for Linux automation operations management, providing 88 tools across 8 categories for file, system, process, network, compression, and package management via SSH connections.
      4
      MIT

    • Miyabi MCP Bundle

      ShunsukeHayashi
      A
      license
      C
      quality
      Not graded
      maintenance
      A comprehensive all-in-one MCP server with 172 tools across 21 categories including Git operations, tmux monitoring, log aggregation, system resource monitoring, and GitHub integration. Features enterprise-grade security, intelligent caching, cross-platform support, and zero-configuration setup for Claude Desktop.
      100
      18 npm
      6
      -

    • AWS Sage

      arunsanna
      A
      license
      C
      quality
      C
      maintenance
      A unified MCP server for AWS that enables natural language infrastructure management, cross-service resource discovery, and dependency mapping. It features 30 intelligent tools for cost optimization, incident investigation, and multi-account operations protected by a robust safety system.
      30
      5
      MIT

    • Zabbix MCP Server

      leroylim
      A
      license
      C
      quality
      F
      maintenance
      Comprehensive MCP server for integrating with Zabbix monitoring systems, providing 90+ API tools across 19 categories for monitoring, alerting, and infrastructure management.
      100
      15
      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.2/5.0

    Scored across 92 tools

    Disambiguation5/5

    Each tool targets a specific resource and action, with clear prefixes (e.g., aws_, azure_, db_) and descriptive names that prevent confusion. Even similar domains like DNS have distinct tools (dns_records vs dns_propagation_check).

    Naming Consistency5/5

    All tool names follow a consistent pattern of prefix_domain_action using lowercase with underscores (e.g., aws_ec2_instances, k8s_pod_logs). Naming is highly predictable and uniform.

    Tool Count1/5

    With 92 tools, the server is massively over-scoped. Despite covering many domains, the sheer number far exceeds typical agent capacity and suggests many overlapping or unnecessary tools (e.g., multiple DNS and network utilities that could be consolidated).

    Completeness5/5

    The tool set covers an extensive range of infrastructure operations: major cloud providers, databases, containers, Kubernetes, networking, storage, security, system administration, CI/CD, IaC, monitoring, and backups. There are no obvious gaps for the stated 'infra-ops' purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources