DocumentDB Migration MCP Server for migrating data to DocumentDB
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"documentdb-migration-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# DocumentDB Migration MCP Server This MCP (Model Context Protocol) server provides tools for migrating data to DocumentDB. It wraps the existing DocumentDB migration tools into an MCP server interface, making them accessible through the MCP protocol. ## Features - **Easy Migration Workflow**: Complete end-to-end migration workflow that combines index management and full load migration - **Full Load Migration**: Migrate data from a source database to DocumentDB in a one-time operation - **Filtered Full Load Migration**: Migrate data with filtering based on TTL - **Change Data Capture (CDC)**: Continuously replicate changes from a source database to DocumentDB - **Resume Token Management**: Get change stream resume tokens for CDC operations - **Automatic Boundary Generation**: Automatically generate optimal boundaries for segmenting collections during migration - **Index Management**: Export, restore, and check compatibility of indexes between MongoDB and DocumentDB - **DMS Configuration Generator**: Generate optimized AWS DMS CloudFormation templates for DocumentDB migrations ## Installation ```bash uvx documentdb-migration-mcp-server@latest ``` ## MCP Server Configuration Add the MCP server to your favorite agentic tools (e.g., for Amazon Q Developer CLI MCP, Claude, etc.) using the following configuration: ```json { "documentdb-migration-mcp-server": { "autoApprove": [ "runEasyMigration", "runFullLoad", "runFilteredFullLoad", "runCDC", "getResumeToken", "generateBoundaries", "dumpIndexes", "restoreIndexes", "showIndexCompatibilityIssues", "showCompatibleIndexes", "generateDMSConfig" ], "disabled": false, "timeout": 60, "command": "uvx", "args": [ "documentdb-migration-mcp-server@latest" ], "env": { "FASTMCP_LOG_LEVEL": "ERROR", "AWS_PROFILE": "default", "AWS_REGION": "us-east-1" }, "transportType": "stdio" } } ``` You can …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.