Verified

Cloud MCP Server

AWS CLI commands executed by AI assistants to interact with over 200 cloud services.

Data last scanned today · Reviewed today

Overview

This server bridges AI agents and the AWS ecosystem by wrapping the AWS CLI directly. Instead of individual API integrations, it provides a flexible pipeline tool that allows Claude to discover, format, and execute cloud commands using the native CLI toolchain, complete with pipe support for utilities like jq and grep. The server features on-demand documentation lookups via help commands and standardized error handling for validation failures. Recent updates include support for streamable HTTP transport for improved compatibility with modern web-based MCP clients.

Our verdict

This server carries a high risk level with a 34/100 security score. The primary concern is that the authentication method and read-only mode support remain unreviewed, meaning the server could potentially execute destructive commands if your IAM policy is too permissive. Additionally, it is community-maintained and has not seen a commit in over 190 days, making it unsuitable for teams requiring active maintenance and security auditing.

Provides access to over 200 AWS services via CLI
Zero direct dependencies reduces supply-chain surface area
Supports piping CLI output through grep and jq
MIT licensed codebase with existing test coverage

Security score of 34/100 indicates significant unreviewed risks
Authentication methods and read-only status are currently unverified
No official maintenance from AWS
Project inactivity with no commits in 192 days

Tools

Tool	Description	Risk
aws_cli_help	Get documentation for any AWS command	low
aws_cli_pipeline	Execute AWS CLI commands with optional pipes (jq, grep, etc.)	high

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›How does the server authenticate with AWS?

The server utilizes the standard AWS credential chain, automatically discovering credentials from environment variables, your local credentials or config files, or IAM roles.

›Can I use a specific AWS profile?

Yes, you can specify an AWS profile by setting the AWS_PROFILE environment variable in your MCP server configuration.

›What tools are provided to interact with AWS services?

The server provides two tools: aws_cli_help to retrieve documentation for any command, and aws_cli_pipeline to execute AWS CLI commands with support for pipes like jq or grep.

›How are permissions managed for the AWS operations?

The server executes commands using your configured AWS credentials, meaning your existing IAM policies directly control what the model is permitted to do.

›Is there a recommended way to isolate the AWS CLI execution?

Yes, you can run the server via Docker to provide stronger isolation by mounting your local AWS configuration files as read-only volumes.

›How do I configure the server for web-based MCP clients?

You should use the streamable-http transport by setting the AWS_MCP_TRANSPORT environment variable to streamable-http, as the sse transport is deprecated.