Skip to main content
Glama
radumalica

infrastructure-mcp

by radumalica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to infrastructure-mcp

No user-submitted related servers found.

    Related Servers

    • Emisar

      AndrewDryga
      F
      license
      Not graded
      quality
      A
      maintenance
      Give AI agents Zero-Trust access to production infrastructure without the risks of granting them shell access. Actions are bounded by policy and an on-host runner.
      330
      -

    • Self-hosted MCP server for

      LeszczynskiKarol
      A
      license
      Not graded
      quality
      D
      maintenance
      Give Claude direct access to your AWS account, SSH into your servers, run shell commands on your laptop, query your databases, and manage PM2 processes — all from a Claude chat. No Claude Code subscription needed. Your keys never leave your machine.
      2
      MIT

    • MCP SSH Orchestrator

      samerfarida
      A
      license
      B
      quality
      A
      maintenance
      Provides policy-driven, auditable SSH access to server fleets for AI assistants with zero-trust security controls, command whitelisting, and comprehensive audit logging to safely manage infrastructure.
      13
      28
      Apache 2.0

    • Shuttle

      enwaiax
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely execute SSH commands on remote servers with connection pooling, session isolation, and a web audit panel.
      4
      MIT

    • Termada

      Islomzoda
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely execute terminal commands with persistent sessions, async jobs, and mission control, while providing a live dashboard for human oversight.
      4
      Apache 2.0
    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.4/5.0

    Scored across 37 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action within its platform (Linux, Docker, Cisco, Proxmox, Grafana, Kubernetes, inventory); overlaps like cisco_backup vs cisco_backup_diff are clearly differentiated by the diff/baseline semantics. No two tools appear to do the same thing.

    Naming Consistency4/5

    All names use snake_case and largely follow a domain-prefix convention (docker_, cisco_, proxmox_, grafana_, kubectl_), which aids predictable grouping. Minor deviations exist: Linux and inventory tools lack a domain prefix, and action/noun phrasing varies (docker_images vs docker_restart), but the set remains readable and predictable.

    Tool Count2/5

    37 tools across seven subsystems is heavy; while each subsystem is reasonably scoped, the total exceeds the 25-tool threshold and forces an agent to filter a large toolset. The breadth is plausible for a multi-platform infra server, but the count is a significant cognitive burden.

    Completeness3/5

    Diagnostic/read coverage is strong across Linux, Docker, Cisco, Proxmox, Grafana, and Kubernetes, with a few safe mutations (restart, start/stop, snapshot). However, no tool supports create/update/delete of core resources (containers, VMs, dashboards, Kubernetes objects, inventory entries) or config pushes, leaving significant lifecycle gaps for an infrastructure management server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources