CLOUD OPERATIONS / Amazon Web Services
AWS DocumentDB MCP Server
Talks to DocumentDB through the package the README launches with uvx.
“An AWS Labs Model Context Protocol (MCP) server for AWS DocumentDB that enables AI assistants to interact with DocumentDB databases.”
01 / THE REASONING
Why this made the selection.
- The README is a single-cluster DocumentDB bridge that starts read-only and refuses writes until --allow-write.
- The connection string is an operator setting, not a tool argument, and the README warns that putting it on the command line exposes it in process listings.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- src/documentdb-mcp-server/README.md
- LICENSE
Our findings
- README contains awslabs.documentdb-mcp-server@latest.
- README contains a uvx command.
- The server talks to one DocumentDB cluster chosen at startup and lets an assistant query that cluster.
- Database tools fail until DOCUMENTDB_CONNECTION_STRING or --connection-string is set. A command-line connection string is visible to other local users in process listings.
- The default is read-only. Writes return a permission error, and aggregation pipelines that contain $out or $merge are blocked.
Not established by this review
- No AWS API call was made.
- The server was not started and its tools were not called.
- A pin does not verify transitive dependencies.
- No tools/list or tool call was made.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
uvx awslabs.documentdb-mcp-server@latest Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Register the uvx command.
- Use credentials for the account you mean.
- The one-line command above is the uvx launch in the README client block at this commit, not a separate installer. It was not run.
Before you start
- uv
- AWS credentials for the service
- A DocumentDB connection string with the database credentials
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"awslabs.documentdb-mcp-server": {
"command": "uvx",
"args": [
"awslabs.documentdb-mcp-server@latest",
],
"env": {
"DOCUMENTDB_CONNECTION_STRING": "mongodb://<username>:<password>@docdb-cluster.cluster-xyz.us-west-2.docdb.amazonaws.com:27017/?tls=true&tlsCAFile=global-bundle.pem&retryWrites=false",
"AWS_PROFILE": "your-aws-profile",
"AWS_REGION": "us-east-1",
"FASTMCP_LOG_LEVEL": "ERROR"
},
"disabled": false,
"autoApprove": []
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Server documentation ↗Checked
https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/src/documentdb-mcp-server/README.md
Supports: Package name and uvx launch
- Repository licence ↗Checked
https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/LICENSE
Supports: Redistribution terms