Aws Cli MCP Server

Most cloud and infrastructure work still happens through a UI a human drives. Aws Cli MCP server moves it into the conversation instead. An MCP server that can generate and execute AWS CLI commands.

The short version

An MCP (Model Context Protocol) server that lets you generate and execute AWS CLI commands directly from Claude.

• Execute AWS CLI commands through the MCP protocol
• Get detailed information about AWS services
• List available AWS services
• Full access to AWS CLI capabilities

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 4 tools. What each one is for:

• execute-aws-command — Execute AWS CLI commands
• Parameters — - command: AWS service (e.g., s3, ec2, lambda)
• get-service-details — Get details about a specific AWS service
• Prerequisites — The Prerequisites tool exposed by this server

What it needs from you

• Node.js (v20 or later recommended) - npm or yarn - AWS CLI installed and configured with credentials - TypeScript

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Aws Cli's toolset — execute-aws-command, Parameters, get-service-details and 1 more — is a fair guide to whether it matches your workflow. It is maintained by IcyKallen; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Aws Cli's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.