Ext Ops Panel
Open dashboard
Comparison

AWS Documentation vs AWS IAM

AWS Documentation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). AWS IAM is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAWS DocumentationAWS IAM
Docker MCP Catalog Listed
Version: sha256:07888232dde9
Forks (GitHub): 1 805
Pulls (Docker Hub): 118 690
Stars (Docker Hub): 2
Stars (GitHub): 9 773
Not marked · First seen
Listed
Version: sha256:84e5e818de90
Forks (GitHub): 1 805
Pulls (Docker Hub): 13 960
Stars (Docker Hub): 0
Stars (GitHub): 9 773
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

AWS Documentation vs AWS IAM
FactAWS DocumentationAWS IAM
Marketplaces that list it11
Stars (GitHub)9 7739 773
Pulls (Docker Hub) (differs)118 690 (better)13 960 (worse)
Forks (GitHub)1 8051 805
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-documentation)On your machine (mcp/iam-mcp-server)
Transportstdiostdio
Tools it declares (differs)429
Environment variables it asks for (differs)Not published4, secrets among them: 1
LicenceApache-2.0Apache-2.0
Repositorygithub.com/awslabs/mcpgithub.com/awslabs/mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

AWS Documentation

In its own words, on Docker MCP Catalog:

Tools to access AWS documentation, search for content, and get recommendations.

AWS IAM

In its own words, on Docker MCP Catalog:

IAM user, role, group, and policy management.

How to run each

AWS Documentation As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-documentation -- docker run -i --rm mcp/aws-documentation

AWS IAM As a local MCP server: Docker image

Claude Code
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --transport stdio awslabs-iam -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY mcp/iam-mcp-server

Requires: AWS_SECRET_ACCESS_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Only AWS Documentation declares

  • read_documentation
  • read_sections
  • recommend
  • search_documentation

Only AWS IAM declares

  • add_user_to_group
  • attach_group_policy
  • attach_user_policy
  • create_access_key
  • create_group
  • create_role
  • create_user
  • delete_access_key
  • delete_group
  • delete_role_policy
  • delete_user
  • delete_user_policy
Show the remaining 17
  • detach_group_policy
  • detach_user_policy
  • get_group
  • get_managed_policy_document
  • get_role_policy
  • get_user
  • get_user_policy
  • list_groups
  • list_policies
  • list_role_policies
  • list_roles
  • list_user_policies
  • list_users
  • put_role_policy
  • put_user_policy
  • remove_user_from_group
  • simulate_principal_policy

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of AWS Documentation publish no settings it asks for, so we do not compare settings.

What it can do: AWS Documentation · What it can do: AWS IAM · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built