Enables querying of AWS resources using boto3 code snippets via a Model Context Protocol (MCP) server.
Enables querying of AWS resources using boto3 code snippets via a Model Context Protocol (MCP) server. Exposed over MCP by the aws resources mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A Model Context Protocol (MCP) server implementation that provides running generated python code to query any AWS resources through boto3.
Everything the assistant can do here goes through one of these:
Input — * code_snippet (string): Python code using boto3 to query AWS resourcesOperations — len, max, min, sorted, filter, map, sum, any, allOther — print, importResources — The Resources tool exposed by this serverTools — The Tools tool exposed by this serverPrerequisites — You'll need AWS credentials with appropriate permissions to query AWS resources. You can obtain these by: 1. Creating an IAM user in your AWS account@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 6 environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_DEFAULT_REGION, ACCESS_KEY_ID, SECRET_ACCESS_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
You'll need AWS credentials with appropriate permissions to query AWS resources. You can obtain these by: 1. Creating an IAM user in your AWS account 2. Generating access keys for programmatic access 3. Ensuring the IAM user has necessary permissions for the AWS services you want to query The following environment variables are required: - AWS_ACCESS_KEY_ID: Your AWS access key -
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Aws Resources's toolset — Input, Operations, Other and 3 more — is a fair guide to whether it matches your workflow. It is maintained by baryhuang; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Input | * code_snippet (string): Python code using boto3 to query AWS resources |
| Operations | len, max, min, sorted, filter, map, sum, any, all |
| Other | print, __import__ |
| Resources | The Resources tool exposed by this server. |
| Tools | The Tools tool exposed by this server. |
| Prerequisites | You'll need AWS credentials with appropriate permissions to query AWS resources. You can obtain these by: 1. Creating an IAM user in your AWS account 2. Generating access keys for programmatic access 3. Ensuring the IAM |
{
"mcpServers": {
"aws-resources": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"AWS_ACCESS_KEY_ID": "your-value",
"AWS_SECRET_ACCESS_KEY": "your-value",
"AWS_SESSION_TOKEN": "your-value",
"AWS_DEFAULT_REGION": "your-value",
"ACCESS_KEY_ID": "your-value",
"SECRET_ACCESS_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
You'll need AWS credentials with appropriate permissions to query AWS resources. You can obtain these by: 1. Creating an IAM user in your AWS account 2. Generating access keys for programmatic access 3. Ensuring the IAM user has necessary permissions for the AWS services you want to query The following environment variables are required: - AWS_ACCESS_KEY_ID: Your AWS access key -
| Variable | Description | Required |
|---|---|---|
| AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| AWS_SESSION_TOKEN | Credential the server authenticates with. | Yes |
| AWS_DEFAULT_REGION | Configuration value read at startup. | Optional |
| ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.