Skip to main content
Glama
lokeswaran-aj

AWS MCP Server

by lokeswaran-aj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to AWS MCP Server

No user-submitted related servers found.

    Related Servers

    • AWS MCP Server

      LokiMCPUniverse
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with AWS services (EC2, S3, Lambda, DynamoDB, etc.) through the Model Context Protocol, allowing natural language management of cloud resources.
      2
      -

    • Aws Claw

      necatiarslan
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a comprehensive suite of tools for interacting with AWS services like S3, EC2, and Lambda using natural language commands. It enables AI assistants to inspect, manage, and operate AWS resources directly through the Model Context Protocol using your local credentials.
      2 npm
      1
      Apache 2.0

    • AWS MCP Server

      MCP-Mirror
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to execute AWS CLI commands and retrieve service documentation through the Model Context Protocol. It supports Unix pipes for output filtering and provides pre-defined prompt templates for common cloud management tasks.
      MIT

    • AWS MCP Server

      ihatesea69
      F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server allowing Claude AI to interact with AWS resources through natural language, enabling users to query and manage AWS services without using the traditional AWS Console or CLI.
      3
      6
      -
    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.1/5.0

    Scored across 54 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific AWS resources and actions, with clear boundaries (e.g., create-vpc vs. update-vpc-attribute). However, some overlap exists in security group operations (authorize/revoke egress/ingress vs. modify-security-group-rules), which could cause minor confusion for agents.

    Naming Consistency5/5

    Tool names follow a highly consistent verb-noun pattern with hyphens throughout (e.g., create-vpc, list-subnets, delete-ami). All 54 tools adhere to this convention, making them predictable and easy to parse.

    Tool Count2/5

    With 54 tools, the count is excessive for a single server, likely overwhelming for agents. While AWS is a broad domain, this feels heavy and could be better scoped into multiple servers (e.g., separate EC2, VPC, S3 servers) for improved usability.

    Completeness5/5

    The tool set provides comprehensive CRUD and lifecycle coverage across AWS services like EC2, VPC, S3, and RDS. It includes creation, listing, updating, and deletion for most resources, with no obvious gaps for core operations, ensuring agents can handle full workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources