Skip to main content
Glama
nhkm95

AWS Infrastructure Operations MCP

by nhkm95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AWS Infrastructure Operations MCP

No user-submitted related servers found.

    Related Servers

    • vps-ops-mcp

      Akdag94
      A
      license
      A
      quality
      A
      maintenance
      A safe, structured MCP server that lets AI inspect and operate a VPS through typed, allowlisted tools for nginx, PM2, SSL, UFW, fail2ban, with read-only defaults and opt-in mutations.
      6
      6 npm
      2
      MIT

    • aws-readonly-mcp

      ziyuyu23
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that lets an LLM inspect an AWS account — list EC2 instances, S3 buckets, IAM users, and cost — with a structural guarantee against any mutations.
      MIT

    • runtime-inspector-mcp

      ludi-uni
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.
      MIT

    • CloudGuard MCP

      kishoreqwerty
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for inspecting AWS resources, detecting misconfigurations, and estimating costs across EC2, S3, and IAM, enabling agents to safely query and analyze cloud infrastructure.
      -
    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 5 tools

    Disambiguation5/5

    Each tool clearly targets a distinct aspect: instance health, metrics, errors, service status, and service journal. There is minimal overlap, and the descriptions specify distinct data sources (CloudWatch, SSM) and resources (EC2 instance vs. service).

    Naming Consistency5/5

    All tool names follow a uniform `get_` prefix followed by a descriptive noun phrase, such as `get_instance_health` and `get_service_journal`. The pattern is consistent and predictable, making the API easy to navigate.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a monitoring-focused infrastructure ops API. Each tool serves a specific operational need, and the count is neither too thin nor bloated for the apparent purpose.

    Completeness4/5

    The tool set covers core monitoring needs: health, metrics, errors, service status, and logs. Minor gaps exist (e.g., no list operations, no instance control), but for a read-only diagnostics server, the coverage is solid and workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources