LABSCO SUMMARY
It uses the credentials already in ~/.aws — no keys pasted into a config file.
That is the practical difference from most cloud bridges: profiles and SSO come from the setup you have, so switching accounts is picking a profile rather than editing secrets. The flip side is scope — it can modify resources, not just describe them, so pick the profile you point it at deliberately.
What it is
A server that lets an assistant query and modify AWS resources in conversation, running locally against your own AWS configuration.
What you get
- Query and modify AWS resources by describing what you want
- Multiple AWS profiles, with SSO authentication supported
- Multi-region operation
- Local execution using your own credentials — nothing is handed to an external service
Requirements
Node.js, and AWS credentials already configured locally in your ~/.aws directory. Clone the repository, install dependencies with pnpm or npm, then point the client at the project directory with the start script. MFA support and SSO credential caching are listed as still in development.
Setup effort
Build from source — git clone https://github.com/RafalWilinski/aws-mcp
USE CASES
01
Finding out what is actually deployed
Ask which Lambda functions are in a region, or list the ECS clusters and their services.
02
Checking storage before a cleanup
List S3 buckets with their sizes instead of clicking through the console.
03
Switching between accounts
List the available profiles and pick the one you mean before asking anything else.
04
Looking across regions
Ask the same question for another region without changing your shell environment.
BEFORE YOU INSTALL
What to know first
Requires
- Node.js
- AWS credentials configured locally (~/.aws/ directory)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/RafalWilinski/aws-mcp
cd aws-mcp
npm installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"aws": {
"command": "npm",
"args": [
"--silent",
"--prefix",
"/Users/<YOUR_USERNAME>/aws-mcp",
"start"
]
}
}
}/Users/<YOUR_USERNAME>/aws-mcp is the path to the aws-mcp folder you cloned. If you installed with pnpm, the command can be pnpm instead of npm.