Skip to main content
Glama
hbmun

MCP AWS Monitor

by hbmun

Related Servers

Alternatives to MCP AWS Monitor

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Provides a comprehensive suite of 76 tools for AWS cloud resource optimization, cost management, and infrastructure monitoring. It enables users to identify unused resources, analyze cost trends, right-size capacity, and maintain security compliance through natural language.
      76
      MIT
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to AWS infrastructure through AWS IAM Identity Center for secure, natural language management of cloud resources across multiple accounts. It enables users to execute AWS CLI commands, monitor resources, and run remote shell commands on EC2 instances via Systems Manager.
      500 npm
      15
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language analysis of AWS cloud costs, waste audits, and budget insights across multiple profiles and regions.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables management and provisioning of AWS resources like EC2, S3, and RDS using natural language prompts through the Model Context Protocol. It allows users to automate complex infrastructure tasks, such as setting up VPCs and security groups, via a chat interface.
      54
      6 npm
      27
      MIT

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a specific AWS resource and action, with clear prefixes per service. For example, cloudwatch_get_alarms and cloudwatch_get_metric are distinct, and even similar actions like list services for EC2, ECS, RDS are separated by service prefix.

    Naming Consistency4/5

    Most tools follow a service_verb_noun pattern, but a few like rds_slow_queries and sqs_queue_detail omit the verb, and cloudwatch_search_logs uses 'search' instead of 'get' or 'list'. Overall, the pattern is mostly consistent and readable.

    Tool Count5/5

    19 tools covering 7 AWS services is well-scoped for a monitoring server. Each service has 2-4 tools, providing essential listing and metric retrieval without unnecessary bloat.

    Completeness4/5

    The tool surface covers key monitoring operations: listing resources, getting metrics, querying logs, and reading files. The generic cloudwatch_get_metric tool fills gaps for unspecified services. Missing some advanced features like CloudWatch dashboards or detailed per-instance metrics, but adequate for common monitoring tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues