# AWS IAM

An MCP server that lets your agent create and edit AWS IAM users, roles, groups and policies, with a simulator to test permissions before anything changes.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 9939 repo stars
- Author: awslabs
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/awslabs/mcp/tree/HEAD/src/iam-mcp-server
- Updated: 2026-10-23
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/aws-iam

## What it does

The server hands the agent tools for everyday IAM work: add a user, build a role with a trust policy, move people between groups, attach or detach a policy, issue and revoke access keys. Inline policies on users and roles can be created, read and deleted as well.

The package is `awslabs.iam-mcp-server`, installed with `uv` or `pip`. In an MCP client such as Cursor, Cline or Zed you register it as `uvx awslabs.iam-mcp-server@latest` and pass `AWS_PROFILE` and `AWS_REGION` in the env block. Windows takes a different entry: `uv` with `tool run --from ...` and the `.exe` name.

Credentials are mandatory. A named profile, a key pair in environment variables or an instance role on EC2 and Lambda all work. The identity behind them needs a broad set of `iam:*` actions covering reads, creates and deletes; a trimmed policy makes those calls fail. Simulate a change before you apply it, and read-only mode blocks edits entirely.

## Requirements
- Needs: Docker
- Works with: AWS

## Install

### Claude Code (native platform)

**Install**
- The MCP registry has no launch command for it: see the repository README

## When to use it
- create an IAM user and hand out an access key
- stand up a role with a trust policy without hand-writing JSON
- test a permission in the simulator before it goes live
- remove a user together with everything attached to it
- keep permissions in groups instead of per-user attachments

## Example prompts
- List every IAM user in the account and the policies attached to each
- Create a role `deploy-role` that EC2 can assume and attach an S3 read policy to it
- Simulate whether the user `ci-bot` can delete objects in the bucket

## Similar
- [aws-iam](https://affpapa.org/en/nevibecode/skills/devops-skills-aws-iam.md) — skill · 368 installs
- [aws-account-management](https://affpapa.org/en/nevibecode/skills/aws-account-management.md) — skill · ★ 301 repo stars
- [mastering-aws-cli](https://affpapa.org/en/nevibecode/skills/mastering-aws-cli.md) — skill · 3000 installs
- [dd-aws-integration](https://affpapa.org/en/nevibecode/skills/dd-aws-integration.md) — skill · 105 installs
- [securing-s3-buckets](https://affpapa.org/en/nevibecode/skills/securing-s3-buckets.md) — skill · 7800 installs
- [launching-ec2-instance-with-best-practices](https://affpapa.org/en/nevibecode/skills/launching-ec2-instance-with-best-practices.md) — skill · 7200 installs

From the same set: [awslabs/mcp](https://affpapa.org/en/nevibecode/by/awslabs/mcp.md) — 36 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
