Ext Ops Panel
Open dashboard
Comparison

Amazon DynamoDB vs io.github.mongodb-js/mongodb-mcp-server

Amazon DynamoDB is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.mongodb-js/mongodb-mcp-server is an MCP server published by mongodb-js. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
MarketplaceAmazon DynamoDBio.github.mongodb-js/mongodb-mcp-server
Docker MCP Catalog Listed
Version: sha256:fbec79079a9b
Forks (GitHub): 1 817
Pulls (Docker Hub): 21 667
Stars (Docker Hub): 0
Stars (GitHub): 9 798
Not marked · First seen
Listed
Version: sha256:6ab64d0ba27f
Forks (GitHub): 298
Pulls (Docker Hub): 156 330
Stars (Docker Hub): 11
Stars (GitHub): 1 146
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 2.1.0
Downloads/month (npm): 503 570
Downloads/week (npm): 100 749
Forks (GitHub): 298
Stars (GitHub): 1 146
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.2.1
Forks (GitHub): 42
Stars (GitHub): 190
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.2.0
Forks (GitHub): 42
Stars (GitHub): 190
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

Amazon DynamoDB vs io.github.mongodb-js/mongodb-mcp-server
FactAmazon DynamoDBio.github.mongodb-js/mongodb-mcp-server
Marketplaces that list it (differs)1 (worse)5 (better)
Stars (GitHub) (differs)9 798 (better)1 146 (worse)
Pulls (Docker Hub) (differs)21 667 (worse)156 330 (better)
Forks (GitHub) (differs)1 817 (better)298 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp/dynamodb-mcp-server)On your machine (mongodb-mcp-server)
Transportstdiostdio
Tools it declares (differs)825
Environment variables it asks for (differs)2, secrets among them: 042, secrets among them: 4
Parts of the bundle (differs)Not a bundle9
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/awslabs/mcpgithub.com/mongodb-js/mongodb-mcp-server
Changes in the last 7 days (differs)04
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

Amazon DynamoDB

In its own words, on Docker MCP Catalog:

Complete DynamoDB operations and table management.

io.github.mongodb-js/mongodb-mcp-server

In its own words, on Official MCP Registry:

MongoDB Model Context Protocol Server

How to run each

Amazon DynamoDB As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio awslabs-dynamodb -- docker run -i --rm mcp/dynamodb-mcp-server

io.github.mongodb-js/mongodb-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "MDB_MCP_API_CLIENT_ID=<YOUR_MDB_MCP_API_CLIENT_ID>" --env "MDB_MCP_API_CLIENT_SECRET=<YOUR_MDB_MCP_API_CLIENT_SECRET>" --env "MDB_MCP_CONNECTION_STRING=<YOUR_MDB_MCP_CONNECTION_STRING>" --env "MDB_MCP_VOYAGE_API_KEY=<YOUR_MDB_MCP_VOYAGE_API_KEY>" --transport stdio mongodb-mcp-server -- npx -y mongodb-mcp-server

Requires: MDB_MCP_API_CLIENT_ID (secret), MDB_MCP_API_CLIENT_SECRET (secret), MDB_MCP_CONNECTION_STRING (secret), MDB_MCP_VOYAGE_API_KEY (secret)

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

Tools each declares

Only Amazon DynamoDB declares

  • compute_performances_and_costs
  • dynamodb_data_model_schema_converter
  • dynamodb_data_model_schema_validator
  • dynamodb_data_model_validation
  • dynamodb_data_modeling
  • generate_data_access_layer
  • generate_resources
  • source_db_analyzer

Only io.github.mongodb-js/mongodb-mcp-server declares

  • aggregate
  • aggregate-db
  • collection-indexes
  • collection-schema
  • collection-storage-size
  • connect
  • count
  • create-collection
  • create-index
  • db-stats
  • delete-many
  • drop-collection
Show the remaining 13
  • drop-database
  • drop-index
  • explain
  • export
  • find
  • insert-many
  • list-collections
  • list-databases
  • list-knowledge-sources
  • mongodb-logs
  • rename-collection
  • search-knowledge
  • update-many

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

Only Amazon DynamoDB asks for

  • AWS_PROFILE
  • AWS_REGION

Only io.github.mongodb-js/mongodb-mcp-server asks for

  • MDB_MCP_ALLOW_REQUEST_OVERRIDES
  • MDB_MCP_API_CLIENT_ID (secret)
  • MDB_MCP_API_CLIENT_SECRET (secret)
  • MDB_MCP_ASSISTANT_BASE_URL
  • MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS
  • MDB_MCP_CONFIRMATION_REQUIRED_TOOLS
  • MDB_MCP_CONNECTION_SCOPE
  • MDB_MCP_CONNECTION_STRING (secret)
  • MDB_MCP_DISABLED_TOOLS
  • MDB_MCP_DISABLE_SERVER_SIDE_JS
  • MDB_MCP_DRY_RUN
  • MDB_MCP_ELICITATION_TIMEOUT_MS
Show the remaining 30
  • MDB_MCP_EXPORTS_PATH
  • MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS
  • MDB_MCP_EXPORT_TIMEOUT_MS
  • MDB_MCP_EXTERNALLY_MANAGED_SESSIONS
  • MDB_MCP_HEALTH_CHECK_HOST
  • MDB_MCP_HEALTH_CHECK_PORT
  • MDB_MCP_HTTP_BODY_LIMIT
  • MDB_MCP_HTTP_HEADERS
  • MDB_MCP_HTTP_HOST
  • MDB_MCP_HTTP_PORT
  • MDB_MCP_HTTP_RESPONSE_TYPE
  • MDB_MCP_IDLE_TIMEOUT_MS
  • MDB_MCP_INDEX_CHECK
  • MDB_MCP_LOGGERS
  • MDB_MCP_LOG_PATH
  • MDB_MCP_MAX_ACTIVE_CONNECTIONS
  • MDB_MCP_MAX_BYTES_PER_QUERY
  • MDB_MCP_MAX_DOCUMENTS_PER_QUERY
  • MDB_MCP_MAX_SESSIONS
  • MDB_MCP_MAX_TIME_M_S
  • MDB_MCP_MCP_CLIENT_LOG_LEVEL
  • MDB_MCP_MONITORING_SERVER_FEATURES
  • MDB_MCP_MONITORING_SERVER_HOST
  • MDB_MCP_MONITORING_SERVER_PORT
  • MDB_MCP_NOTIFICATION_TIMEOUT_MS
  • MDB_MCP_PREVIEW_FEATURES
  • MDB_MCP_READ_ONLY
  • MDB_MCP_TELEMETRY
  • MDB_MCP_TRANSPORT
  • MDB_MCP_VOYAGE_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Amazon DynamoDB · What it can do: io.github.mongodb-js/mongodb-mcp-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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