AWS Bedrock Data Automation vs Nutrient Document Engine MCP Server
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Nutrient Document Engine MCP Server is an MCP server published by PSPDFKit. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
| Marketplace |  AWS Bedrock Data Automation |  Nutrient Document Engine MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 808 Pulls (Docker Hub): 14 357 Stars (Docker Hub): 0 Stars (GitHub): 9 782 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.0.3 Downloads/month (npm): 208 Downloads/week (npm): 38 Forks (GitHub): 4 Stars (GitHub): 62 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
| Fact | AWS Bedrock Data Automation | Nutrient Document Engine MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 782 (better) | 62 (worse) |
| Pulls (Docker Hub) (differs) | 14 357 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 808 (better) | 4 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | On your machine (@nutrient-sdk/document-engine-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 5, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/pspdfkit/nutrient-document-engine-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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 Bedrock Data Automation
Analyze documents, images, videos, and audio.
Nutrient Document Engine MCP Server
MCP server for self-hosted Nutrient Document Engine: extract, edit, redact, and annotate documents.
How to run each
AWS Bedrock Data Automation As a local MCP server: Docker image
claude mcp add --transport stdio aws-bedrock-data-automation -- docker run -i --rm mcp/aws-bedrock-data-automation-mcp-serverNutrient Document Engine MCP Server As a local MCP server: npm package
claude mcp add --env "DASHBOARD_PASSWORD=<YOUR_DASHBOARD_PASSWORD>" --env "DOCUMENT_ENGINE_API_AUTH_TOKEN=<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>" --env "DOCUMENT_ENGINE_BASE_URL=<YOUR_DOCUMENT_ENGINE_BASE_URL>" --transport stdio nutrient-document-engine-mcp-server -- npx -y @nutrient-sdk/document-engine-mcp-serverRequires: DASHBOARD_PASSWORD (secret), DOCUMENT_ENGINE_API_AUTH_TOKEN (secret), DOCUMENT_ENGINE_BASE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Nutrient Document Engine MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Bedrock Data Automation asks for
AWS_BUCKET_NAMEAWS_PROFILEAWS_REGION
Only Nutrient Document Engine MCP Server asks for
DASHBOARD_PASSWORD (secret)DASHBOARD_USERNAMEDOCUMENT_ENGINE_API_AUTH_TOKEN (secret)DOCUMENT_ENGINE_BASE_URLLOG_LEVEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Bedrock Data Automation · What it can do: Nutrient Document Engine 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.