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
      A
      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.
      1
      3
      296
      ISC
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 28 tools

    Disambiguation4/5

    Tools cluster into clearly labeled groups—auth/session, resource CRUD via Cloud Control, logs/metrics, docs, and generic invocation—so an agent can usually select the right one. Minor overlaps exist: aws_session_get vs aws_whoami both report current identity/state, and aws_call, aws_paginate, aws_multi_region, and aws_multi_account are related generic-call variants, though their descriptions draw distinct boundaries.

    Naming Consistency4/5

    All tools share the aws_ prefix and use lowercase snake_case, with a mostly verb-first pattern (aws_session_set, aws_resource_list, aws_logs_query, aws_docs_search). A few names are non-verb phrases or nouns (aws_whoami, aws_script, aws_multi_region, aws_refresh_if_expiring_soon), but they do not break the overall predictability.

    Tool Count2/5

    At 28 tools this exceeds the 25-tool threshold the rubric treats as too many for typical MCP servers, even accounting for AWS's breadth. The set is organized and each tool has a defined role, with clusters like 8 auth/session tools and 7 resource_* tools that could arguably be consolidated, but the menu load is heavy for an agent.

    Completeness5/5

    The generic aws_call plus aws_paginate provides a universal escape hatch for any AWS API, so no operation is unreachable. Dedicated tools cover the common high-friction workflows—SSO login lifecycle, Cloud Control resource CRUD, CloudWatch Logs query/tail, Metrics Insights, Lambda invoke with log tail, IAM simulation, docs search/read, and multi-region/multi-account fan-out with no obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources