Skip to main content
Glama
YawLabs

@yawlabs/aws-mcp

Official
by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @yawlabs/aws-mcp

No user-submitted related servers found.

    Related Servers

    • AWS-Auth

      N0mansky
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AWS SSO authentication and profile management, enabling AI assistants to check identity, switch profiles, and manage EC2/EKS resources.
      8
      MIT

    • ghost-dev-mcp

      KiOnCloud
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server on AWS Lambda that gives AI assistants read-only access to SQS dead-letter queues and CloudWatch logs for fast incident triage.
      -

    • aws-mcp

      RafalWilinski
      F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with your AWS environment. This allows for natural language querying and management of your AWS resources during conversations. Think of better Amazon Q alternative.
      3
      295
      -
    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

    A4.4/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target distinct resources/actions (auth, session, docs, resource CRUD, logs, metrics, IAM). There is mild overlap among the generic API runners (aws_call, aws_paginate, aws_multi_region, aws_multi_account) and between aws_logs_tail and aws_logs_query, but the descriptions explicitly state when to prefer each, so misselection risk is low.

    Naming Consistency5/5

    Every tool uses a consistent snake_case verb_noun pattern with a uniform aws_ prefix (aws_whoami, aws_login_start, aws_resource_get, aws_metrics_query, etc.). The grouping by domain (login_*, session_*, resource_*, logs_*) is predictable and readable throughout.

    Tool Count4/5

    28 tools is on the heavy side, but the server spans genuinely distinct AWS domains (auth, session, docs, generic API, pagination, multi-region/account fan-out, Cloud Control CRUD, logs, metrics, IAM, Lambda, scripting), so most tools earn their place. It stays under the extreme-mismatch threshold.

    Completeness5/5

    The surface covers the full lifecycle: auth verification/login/refresh, session profile+region management, arbitrary API access with pagination and fan-out, Cloud Control create/read/update/delete plus status polling and a dry-run diff, observability (logs tail/query, metrics), IAM simulation, Lambda invoke, docs, and an orchestration escape hatch. No obvious dead ends for the domain.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources