Ext Ops Panel
Open dashboard
Comparison

AWS IAM vs tigris-storage

AWS IAM is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). tigris-storage is a plugin bundle for AI coding tools published by tigrisdata. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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 IAMtigris-storage
Docker MCP Catalog Listed
Version: sha256:84e5e818de90
Forks (GitHub): 1 806
Pulls (Docker Hub): 14 012
Stars (Docker Hub): 0
Stars (GitHub): 9 779
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
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 IAM vs tigris-storage
FactAWS IAMtigris-storage
Marketplaces that list it11
Stars (GitHub) (differs)9 779 (better)1 (worse)
Pulls (Docker Hub) (differs)14 012No figure on Docker Hub
Forks (GitHub) (differs)1 806 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/iam-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)29Not published
Environment variables it asks for (differs)4, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle8
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/awslabs/mcpgithub.com/tigrisdata/tigris-agents-plugins
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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 IAM

In its own words, on Docker MCP Catalog:

IAM user, role, group, and policy management.

tigris-storage

In its own words, on Claude Code: claude-plugins-community:

Tigris object storage integration — CLI reference for bucket management, object operations, access keys, IAM, and migrations. Skills cover authentication, CORS, presigned URLs, snapshots, forks, shadow bucket migrations, lifecycle rules, and notifications.

How to run each

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)

tigris-storage As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tigris-storage@claude-community

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

Tools each declares

The marketplaces of tigris-storage publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of tigris-storage publish no settings it asks for, so we do not compare settings.

What it can do: AWS IAM · What it can do: tigris-storage · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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