AWS IAM MCP
Official AWS Labs MCP for IAM administration: users, roles, groups, policies, inline policies, access keys, and policy simulation. Read-only mode supported via --allow-write opt-in pattern. Apache-2.0 within awslabs/mcp monorepo.
“Official AWS Labs MCP for IAM administration: users, roles, groups, policies, inline policies, access keys, and policy simulation. Read-only mode is supported via the --allow-write opt-in pattern. 5 commits on the server path in the last 30 days. Apache-2.0 with AWS Labs official-vendor signal.”
INSTALL THIS SERVER
{
"mcpServers": {
"awslabs.iam-mcp-server": {
"command": "uvx",
"args": [
"awslabs.iam-mcp-server@latest"
],
"env": {
"AWS_PROFILE": "default",
"AWS_REGION": "us-east-1"
}
}
}
}
{
"mcpServers": {
"awslabs.iam-mcp-server": {
"command": "uvx",
"args": [
"awslabs.iam-mcp-server@latest"
],
"env": {
"AWS_PROFILE": "default",
"AWS_REGION": "us-east-1"
}
}
}
}
{
"mcpServers": {
"awslabs.iam-mcp-server": {
"command": "uvx",
"args": [
"awslabs.iam-mcp-server@latest"
],
"env": {
"AWS_PROFILE": "default",
"AWS_REGION": "us-east-1"
}
}
}
}
{
"mcpServers": {
"awslabs.iam-mcp-server": {
"command": "uvx",
"args": [
"awslabs.iam-mcp-server@latest"
],
"env": {
"AWS_PROFILE": "default",
"AWS_REGION": "us-east-1"
}
}
}
}
{
"mcpServers": {
"awslabs.iam-mcp-server": {
"command": "uvx",
"args": [
"awslabs.iam-mcp-server@latest"
],
"env": {
"AWS_PROFILE": "default",
"AWS_REGION": "us-east-1"
}
}
}
}
7 TOOLS AVAILABLE
OUR ASSESSMENT
- 5 commits on the server path in the last 30 days.
- Apache-2.0 licence.
- Official AWS Labs maintenance.
- Policy simulation surface for testing permissions before applying.
- Force-delete capability handles users with associated resources.
- Permissions Boundary support for enhanced security guardrails.
- Trust policy validation runs JSON validation before submission.
- Read-only default with explicit --allow-write opt-in.
- IAM mistakes carry blast-radius risk; broad MCP access to mutating IAM operations carries significant operational risk.
- AWS account-level scoping; multi-account IAM administration runs separate MCP instances per account.
- Policy simulation depends on accurate input policies; results reflect the simulated state, distinct from live evaluation.
- 5 commits on the path in the last 30 days, modest cadence.
IAM is the security-critical control plane of an AWS account; MCP access carries the same blast radius. Default to --allow-write off. Run the MCP under a dedicated AWS profile with IAM administration scoped to a least-privilege admin role (avoid root). Use Permissions Boundaries on any roles the MCP creates to enforce that the boundary applies to created principals. For production environments, restrict the MCP to read-only and use it for diagnostic surfaces (who has access, what does this policy grant), then apply changes through a separate, audit-logged path.
AWS shops where IAM administration is part of operator workflows and an MCP entry point would speed up routine queries (who has access to what, what does this policy grant in effect); permission auditing flows that simulate policy effects before applying them; read-only IAM diagnostic agents that surface policy attachments and effective permissions.
TECHNICAL DETAILS
ADOPTION METRICS
// Reading this8,924 stars on the awslabs/mcp parent monorepo. 5 commits on the IAM server path in the last 30 days.
// Reading thisFourth-ranked in security. Tier 2 cadence; Tier 1 vendor signal.
SOURCES & VERIFICATION
We don't take any single directory's word for it. Before scoring, we cross-reference 4 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.
The same server, 4 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.
| Source | Their rating | Their star count | Their downloads | Last synced |
|---|---|---|---|---|
| AutomationSwitch This page | 4.1editorial | 8,924 | — | MAY 1, 2026 |
| PulseMCP | — unrated | unavailable | unavailable | MAY 1, 2026 |
| MCP.so | — unrated | unavailable | unavailable | MAY 1, 2026 |
| Glama | — unrated | unavailable | unavailable | MAY 1, 2026 |
| Official MCP Registry | — unrated | unavailable | unavailable | MAY 1, 2026 |
// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.
OTHER SECURITY MCP SERVERS
Prowler MCP
Cloud Security Posture Management (CSPM) platform with 1000+ security checks across multiple cloud providers and 70+ compliance frameworks, exposed through MCP. Three deployment options: Prowler Cloud (recommended), local stdio, self-hosted HTTP. 13,717 stars, Apache-2.0.
Auth0 MCP Server
Official Auth0 MCP server connecting Claude, Cursor, Windsurf, VS Code, and Gemini to Auth0 Management APIs. Create apps, deploy Actions, debug logs, and query users with natural-language commands. Read-only mode and tool-glob filtering supported. Beta software per Auth0.
HashiCorp Vault MCP
Official HashiCorp MCP for Vault: secrets, mounts, KV, and PKI management with stdio and Streamable HTTP transports. 9 commits on main in the last 30 days. MPL-2.0 with HashiCorp official-vendor signal.
AWS CloudTrail MCP
Official AWS Labs MCP for CloudTrail: 90 days of management events via lookup_events and Trino-compatible SQL queries against CloudTrail Lake Event Data Stores. 3 commits on the server path in the last 30 days. Pairs with the IAM MCP for security audit workflows.
Infisical MCP
Official Infisical MCP server for secrets management. 10 tools cover the full secret lifecycle plus project, environment, folder, and member management. Two authentication methods (machine identity universal-auth and access-token), self-hostable instance support via INFISICAL_HOST_URL.
Trivy MCP
Official Aqua Security Trivy plugin that turns Trivy scanning capabilities into an MCP server. Distributed as a Trivy plugin: `trivy plugin install mcp`. Three transport modes (stdio, streamable HTTP, SSE), IDE integration for VS Code, Cursor, JetBrains, and Claude Desktop.
DISCUSS YOUR
MCP REQUIREMENTS.
Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.