Skip to main content
Glama
rishikavikondala

AWS MCP Server

by rishikavikondala
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AWS MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • S3 MCP Server

      samuraikun
      A
      license
      A
      quality
      F
      maintenance
      An Amazon S3 Model Context Protocol server that allows Large Language Models like Claude to interact with AWS S3 storage, providing tools for listing buckets, listing objects, and retrieving object contents.
      3
      601 npm
      30
      MIT

    • 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
      -

    • MCP File Operations Server

      Kavishankarks
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude Desktop to perform file operations like reading, writing, listing directories, and managing files through natural language commands.
      MIT
    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

    A3.5/5.0

    Scored across 23 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The DynamoDB tools are precisely scoped to specific operations (batch_execute, batch_get, describe_ttl, etc.), and S3 tools are similarly well-defined (bucket_create, object_read, etc.). There is no overlap where an agent would struggle to choose between tools.

    Naming Consistency5/5

    All tool names follow a consistent pattern of service_operation format (e.g., dynamodb_item_get, s3_object_upload). The naming is uniformly snake_case with clear verbs (get, put, delete, list, create, update) that match the operations precisely, making it highly predictable and readable.

    Tool Count4/5

    With 23 tools, the count is slightly high but reasonable for covering two major AWS services (DynamoDB and S3). It provides comprehensive operations for each service, though it might feel heavy for a single server. The scope is well-defined, and each tool serves a distinct function, justifying its inclusion.

    Completeness5/5

    The tool set offers complete CRUD/lifecycle coverage for both DynamoDB and S3 domains. For DynamoDB, it includes table management (create, describe, list, update, delete) and item operations (get, put, update, delete, query, scan, batch operations, TTL). For S3, it covers bucket management (create, list, delete) and object operations (upload, read, list, delete). No obvious gaps exist for core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources