by AWS
Updated October 19, 2026
MCP100 verdict
Not currently recommended. Shortlist — editorially admitted, not a Recommended endorsement.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Cloud operations
Trust
Status warning
Separate identity from AWS Documentation MCP; recommend least-privilege IAM
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
2.9k shared-repository stars · not MCP-specific
83,740 shared-package downloads / 30 days · not MCP-specific · Third-party: PyPI Stats
Repository identity: aws/agent-toolkit-for-aws
Package identity: mcp-proxy-for-aws-cli · version 1.7.0
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Official AWS Agent Toolkit is the current AWS-supported repository bundling AWS MCP Server configuration, plugins, and skills. The AWS MCP Server itself is managed, so whole-toolkit stars are shared/distribution evidence and not server-specific adoption.
This is AWS's supported client-side proxy used to connect MCP clients to IAM/SigV4-protected AWS MCP endpoints. It is adjacent connection tooling, not the managed AWS MCP Server package, so downloads are not MCP-server-specific.
Publisher activity observed October 19, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-19
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
{"url":"https://aws-mcp.us-east-1.api.aws/mcp"}Capability
AWS MCP is a AWS MCP integration for aws resource administration via unified mcp. Use for AWS operational workflows requiring more than documentation lookup. General AWS action surface can modify cloud resources and incur cost.
AWS account/role, enabled services, and remote tool surface affect count
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://aws-mcp.us-east-1.api.aws/mcp
Reviewed access
Related reviewed MCPs
Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Choose this instead if
Choose Terraform MCP instead if connect compatible AI clients to HashiCorp's documented MCP capabilities.
Recommended after reviewed Batch 1 correction: exact 61-tool contract closes the prior formal Recommended gap.
Connect agents to Azure resources and more than forty Azure services.
Choose this instead if
Choose Azure MCP Server instead if discovering and inspecting resources across supported Azure services.
Connect agents to Azure resources and more than forty Azure services.
Access supported Cloudflare developer platform capabilities.
Choose this instead if
Choose Cloudflare MCP instead if searching and executing supported Cloudflare API operations across Workers, DNS, R2, Zero Trust, and related products.
Access supported Cloudflare developer platform capabilities.
AWS is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
Use the Agent Toolkit directly from your terminal with the AWS CLI:
aws configure agent-toolkit
See the AWS CLI integration guide for setup, configuration, and usage instructions.
The plugins are available on the official Anthropic marketplace (claude-plugins-official) which is added to your Claude Code installation by default.
Use the following commands to install supported plugins from the toolkit:
For aws-core that covers service selection, CDK/CloudFormation, serverless, containers, storage, observability, billing, SDK usage, and deployment:
/plugin install aws-core@claude-plugins-official
Tip: If you get
Plugin not found, update your local marketplace index first:/plugin marketplace update claude-plugins-official
For aws-agents that covers building AI agents on AWS with Amazon Bedrock and AgentCore:
/plugin install aws-agents@claude-plugins-official
For aws-data-analytics that covers data lake, analytics, and ETL workflows with S3 Tables, AWS Glue, and Athena:
/plugin install aws-data-analytics@claude-plugins-official
For aws-agents-for-devsecops used to investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.
/plugin marketplace add aws/agent-toolkit-for-aws
/plugin install aws-agents-for-devsecops
/reload-plugins
# Or from Claude's official marketplace:
/plugin install aws-agents-for-devsecops@claude-plugins-official
/reload-plugins
# Setup:
/aws-agents-for-devsecops:setup
For aws-startup-advisor that covers startup-focused architecture, cost, security, and AWS Activate guidance, plus migrations to AWS from Azure, GCP, Heroku, and AI stacks such as OpenAI and Gemini, install from this repository's marketplace:
/plugin marketplace add aws/agent-toolkit-for-aws
/plugin install aws-startup-advisor@agent-toolkit-for-aws
/reload-plugins
In your terminal:
codex plugin marketplace add aws/agent-toolkit-for-aws
Then launch Codex and run /plugins to browse and install the aws-core plugin.
Add this repository as a team marketplace from Settings → Plugins → Team Marketplaces → Add Marketplace → Import from Repo, pointing it at aws/agent-toolkit-for-aws. Cursor indexes the plugins listed in .cursor-plugin/marketplace.json on import.
Then open the Plugins panel and install the aws-core plugin (start here), or aws-agents and aws-data-analytics as needed. Each plugin bundles the AWS MCP Server configuration and agent skills.
In your terminal:
devin plugins install aws/agent-toolkit-for-aws#plugins/aws-core
This requires devin auth login and adds the plugin to your personal plugins, so it also loads in Devin cloud sessions and Devin Desktop. Add --local to install on this machine only. To install a different plugin, replace aws-core with its name from Plugins, such as aws-agents or aws-data-analytics.
In the Devin web app, choose Customize → Plugins → Add plugin → From repository, enter aws/agent-toolkit-for-aws, and set the subdirectory to plugins/aws-core (or another plugin's directory). Personal plugins added there are also available in the Devin CLI and Devin Desktop.
Kiro setup has two independent parts: the AWS MCP Server (for runtime AWS API access and documentation search) and local skills (for task-specific agent guidance). They complement each other but work independently — skills don't require the MCP server, and the MCP server doesn't serve locally-installed skills.
1. Add the AWS MCP Server to your Kiro MCP configuration (.kiro/settings/mcp.json):
{
"mcpServers": {
"aws": {
"command": "uvx",
"args": [
"mcp-proxy-for-aws-cli@latest",
"https://aws-mcp.us-east-1.api.aws/mcp",
"--metadata",
"AWS_REGION=us-west-2"
]
}
}
}
The MCP server gives your agent access to AWS APIs, sandboxed script execution, and real-time documentation search.
2. Install skills from this repository:
npx skills add aws/agent-toolkit-for-aws/skills
This installs skill files to ~/.kiro/skills/ (global) or .kiro/skills/ (project-level). Each skill is a directory containing a SKILL.md file and optionally a references/ subdirectory with additional context the agent reads from the local filesystem when needed. Kiro discovers installed skills automatically and activates them on demand when a task matches.
Prerequisites: You need uv installed. An AWS account with credentials configured locally is required for API calls and script execution, but not for documentation search or skill discovery. See the user guide for detailed setup instructions.
fx setup has the same two independent parts as Kiro: the AWS MCP Server (for runtime AWS API access and documentation search) and local skills (for task-specific agent guidance). Skills don't require the MCP server, and the MCP server doesn't serve locally-installed skills.
1. Add the AWS MCP Server from your terminal. fx stores MCP servers in ~/.fx/mcp.json, so the server is available in every project:
fx mcp add aws uvx mcp-proxy-for-aws-cli@latest https://aws-mcp.us-east-1.api.aws/mcp --metadata AWS_REGION=us-west-2
Or add it to ~/.fx/mcp.json by hand. fx uses the mcp key rather than mcpServers, type to select the transport, and a single command array holding the executable and its arguments:
{
"mcp": {
"aws": {
"type": "local",
"command": [
"uvx",
"mcp-proxy-for-aws-cli@latest",
"https://aws-mcp.us-east-1.api.aws/mcp",
"--metadata",
"AWS_REGION=us-west-2"
]
}
}
}
If a session is already open when you edit the file, run /mcp reload to pick up the change. The MCP server gives your agent access to AWS APIs, sandboxed script execution, and real-time documentation search.
2. Install skills from this repository:
npx skills add aws/agent-toolkit-for-aws/skills -a fx
This installs skill files to .fx/skills/ (project-level); add -g to install to ~/.fx/skills/ (global). fx also discovers skills already installed for other agents in .agents/skills/, .claude/skills/, and .codex/skills/, so a project set up for Codex or Claude Code needs no second copy. Each skill is a directory containing a SKILL.md file and optionally a references/ subdirectory with additional context the agent reads from the local filesystem when needed. fx reads skill metadata at startup and loads a skill's instructions when you or the agent invokes it; type $ in the composer or run /skills to browse what's installed.
Prerequisites: You need uv installed. An AWS account with credentials configured locally is required for API calls and script execution, but not for documentation search or skill discovery. See the user guide for detailed setup instructions.
See the AWS MCP Server getting started guide for instructions on configuring the AWS MCP Server with your agent.
Then install skills from this repository:
npx skills add aws/agent-toolkit-for-aws/skills
Prerequisites: You need uv installed. An AWS account with credentials configured locally is required for API calls and script execution, but not for documentation search or skill discovery. See the user guide for detailed setup instructions.
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
Help AI coding agents build, deploy, and manage applications on AWS.
The Agent Toolkit for AWS gives AI coding agents the tools, knowledge, and guardrails they need to work with AWS services. It works with the coding agents developers already use — including Claude Code, Codex, Cursor, Devin, Kiro, and fx.
Plugins bundle the AWS MCP Server configuration and agent skills into a single install for your coding agent.
| Plugin | Description |
|---|---|
| aws-core | Core AWS skills and MCP Server configuration. Covers service selection, CDK/CloudFormation, serverless, containers, storage, observability, billing, SDK usage, and deployment. Start here. |
| aws-agents | Skills for building AI agents on AWS with Amazon Bedrock and AgentCore. |
| aws-data-analytics | Skills for data lake, analytics, and ETL workflows with S3 Tables, AWS Glue, and Athena. |
| aws-agents-for-devsecops | Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent. |
| aws-startup-advisor | Puts an AWS Startups Solutions Architect in your coding assistant. Recommends the smallest architecture for your stage, credits, and team, then can scaffold it, migrate you from Azure, Google Cloud, or Heroku, move model calls to Amazon Bedrock, investigate production incidents, answer AWS Activate credits eligibility questions, and find startup offers you can use. |
Plugins are currently available for Claude Code, Codex, Cursor, and Devin. For other agents, configure the AWS MCP Server directly and install skills from this repository.
Agent skills are curated packages of instructions and reference materials that help agents complete specific AWS tasks. Skills are loaded on demand — agents discover and retrieve only what's relevant to the current task.
npx skills add aws/agent-toolkit-for-aws/skills
Browse the skills/ directory to see all available skills.
Recommended project-level configuration files that tell agents how to use AWS most effectively — for example, by using the AWS MCP Server, discovering available skills, or searching documentation before acting.
See rules/ for details.
The AWS MCP Server is a managed server that gives agents access to AWS through the Model Context Protocol. It provides:
For details on operation, available tools, authentication, and supported Regions, see the AWS MCP Server documentation.
In 2025, AWS began releasing MCP servers, skills, and plugins as part of AWS Labs. The Agent Toolkit for AWS is the successor to those tools. We recommend using the Agent Toolkit for AWS, because it offers key features including:
AWS Labs MCP servers, skills, and plugins will continue to work and accept contributions, and over time the best of AWS Labs will be transitioned to the Agent Toolkit for AWS to ensure that customers can access the broadest array of tooling and guidance for their agents.
This project is licensed under the Apache-2.0 License. See LICENSE for details.