Amazon DocumentDB with MongoDB compatibility MCP Server
Amazon DocumentDB is a fully managed, scalable, and highly available database service from Amazon Web Services (AWS) designed for document workloads.
Quick Start Summary
The Amazon DocumentDB with MongoDB compatibility MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Amazon DocumentDB with MongoDB compatibility API through natural language. It exposes 10 API endpoints as callable tools, such as GET_AddSourceIdentifierToSubscription, POST_AddSourceIdentifierToSubscription, GET_AddTagsToResource, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/amazonaws-com-docdb. This integration is sourced from the auto Amazon DocumentDB with MongoDB compatibility OpenAPI specification (v2014-10-31) and has a quality score of 46/99 (fair documentation coverage).
Server Details
- Category
- Databases
- Authentication
- None
- Endpoints
- 10 operations
- Transport
- STDIO
- Spec Version
- v2014-10-31
- Install Command
npx -y @mcp/amazonaws-com-docdb
Environment Variables
AMAZON_DOCUMENTDB_WITH_MONGODB_COMPATIBILITY_API_KEYExample: your_amazon_documentdb_with_mongodb_compatibility_api_key
Top Endpoints
/#Action=AddSourceIdentifierToSubscriptionGET_AddSourceIdentifierToSubscription
/#Action=AddSourceIdentifierToSubscriptionPOST_AddSourceIdentifierToSubscription
/#Action=AddTagsToResourceGET_AddTagsToResource
/#Action=AddTagsToResourcePOST_AddTagsToResource
/#Action=ApplyPendingMaintenanceActionGET_ApplyPendingMaintenanceAction
One-Click Install
Copy the snippet for your MCP client and paste it in — zero editing required.
Claude Desktop
Add to claude_desktop_config.json
{
"mcpServers": {
"amazonaws-com-docdb": {
"command": "npx",
"args": [
"-y",
"@mcp/amazonaws-com-docdb"
],
"env": {
"AMAZON_DOCUMENTDB_WITH_MONGODB_COMPATIBILITY_API_KEY": "your_amazon_documentdb_with_mongodb_compatibility_api_key"
}
}
}
}Cursor
Settings → MCP Servers → Add
{
"mcpServers": {
"amazonaws-com-docdb": {
"url": "https://mcpbridge.org/config/amazonaws-com-docdb.json"
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code
Use with MCP extension
{
"mcpServers": {
"amazonaws-com-docdb": {
"url": "https://mcpbridge.org/config/amazonaws-com-docdb.json"
}
}
}Endpoints Explorer
Search and browse the 10 operations supported by this server.
Multi-Language Code Examples
Executable code snippets for calling Amazon DocumentDB with MongoDB compatibility endpoints in curl, TypeScript, or Python.
curl -X GET "https://api.apis.guru/v2/specs/amazonaws.com/docdb/2014-10-31/#Action=AddSourceIdentifierToSubscription" \ -H "Content-Type: application/json" \ # No auth required
Manual Configuration
Directly add this block to your JSON config file, or use the hosted config registry URL.
{
"mcpServers": {
"amazonaws-com-docdb": {
"command": "npx",
"args": ["-y","@mcp/amazonaws-com-docdb"],
"env": {
"AMAZON_DOCUMENTDB_WITH_MONGODB_COMPATIBILITY_API_KEY": "your_amazon_documentdb_with_mongodb_compatibility_api_key"
}
}
}
}Authentication Details
No authentication required. This MCP server runs out-of-the-box.
Documentation Links
Error Handling & HTTP Status Code Matrix
Common status codes, error causes, and resolution steps when invoking Amazon DocumentDB with MongoDB compatibility endpoints.
400 Bad RequestCause: Malformed payload parameters or missing required fields.
Resolution: Verify request schema in Endpoints tab before calling tool.
401 UnauthorizedCause: Missing or invalid API key credentials.
Resolution: Set environment variable in MCP client config under env object.
403 ForbiddenCause: Insufficient scope permissions for requested resource.
Resolution: Verify key permissions in developer dashboard.
404 Not FoundCause: Resource URL path or requested entity ID does not exist.
Resolution: Check path variables and parameters.
429 Rate Limit ExceededCause: API rate limit quota exceeded.
Resolution: Implement exponential backoff retry in tool call.
500 Internal ErrorCause: Upstream server runtime fault.
Resolution: Inspect STDIO stderr output for log trace.
Quality Score
Checked against our protocol-compliance rules.
Specification Version: v2014-10-31
Page compiled on: June 13, 2026
Own this API?
Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.
Option 1: Free Verification
Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.
- • Verified badge on page
- • Standard search sorting
- • 2-3 business days review
Option 2: Featured Upgrade($9/mo)
Instant verification plus premium styling, featured badges, and directory placement boost.
- • ★ Featured star & amber highlight border
- • Top of directory search placement
- • Instant activation via claim token
📖 Detailed MCP Integration Guide
A technical breakdown of capabilities, agent workflows, and security/configuration best practices.
CopyDBClusterSnapshot and ApplyPendingMaintenanceAction actions. Similarly, "Tag our new development cluster 'dev-01' with the environment tag and add the current Git commit as the source identifier to our change-data-capture subscription" would utilize the AddTagsToResource and AddSourceIdentifierToSubscription endpoints. The agent can automate routine tasks such as preparing a database environment for a new team member by copying a parameter group, or applying a critical security update via a maintenance action, all through conversational instructions that are validated and executed as structured API calls.rds:AddTagsToResource, rds:CopyDBClusterSnapshot) on the targeted resources, rather than broad administrative access. Configuration should involve setting up secure credential storage (like AWS Secrets Manager) and ensuring the MCP server environment is configured to use these credentials safely. It is imperative to never expose long-term AWS access keys directly and to use temporary credentials or IAM roles where possible, especially in cloud-hosted MCP server deployments.Similar APIs
Other APIs in the Databases category.
PostgreSQL (MCP)
Query and manage PostgreSQL databases directly from your AI agent. Read schemas, run queries, and manage data.
Database CredentialsNotion API
The Notion API is a comprehensive RESTful interface provided by Notion, the popular all-in-one workspace platform, enabling programmatic interaction with its rich set of collaborative objects. It grants developers and automated systems the ability to read, create, update, and manage core Notion entities such as blocks (the fundamental building blocks of content like text, lists, and media), databases (structured tables with properties), pages (containers for content and databases), and comments. Typical use cases span enterprise and consumer scenarios, including automating team workflows, syncing data between Notion and other business systems (like CRM, project management, or analytics tools), building custom dashboards, generating dynamic reports, and enhancing content collaboration through programmatic updates. Organizations leverage this API to break down data silos, enforce process automation, and create tailored integrations that extend Notion's native capabilities for specific departmental or cross-functional needs.
Amazon CloudWatch Application Insights
Amazon CloudWatch Application Insights is a specialized observability service provided by Amazon Web Services (AWS) designed to simplify the monitoring and troubleshooting of applications, particularly those built on Microsoft IIS and .NET frameworks running on EC2 instances or within Elastic Beanstalk environments. Its core capability lies in automatically discovering application components, analyzing correlated metrics, logs, and traces to identify anomalies, and then surfacing actionable insights that pinpoint the root cause of common operational issues. By integrating seamlessly with other AWS services like CloudWatch, AWS X-Ray, and AWS Systems Manager, it provides a unified view of application health, reducing the mean time to resolution (MTTR) for performance degradations and errors. The typical use case spans enterprise environments managing distributed microservices or monolithic .NET applications, where teams need to proactively detect issues such as memory leaks, high CPU utilization, or specific application errors without manually configuring complex monitoring dashboards and alarms.
Application Auto Scaling
The Application Auto Scaling API, provided by Amazon Web Services (AWS), is a robust service designed to automate the scaling of computing resources for a wide array of AWS services, ensuring optimal performance, availability, and cost efficiency. Its core capability is to define policies that automatically adjust the provisioned capacity of supported resources in response to changing demand, as measured by CloudWatch metrics or predefined schedules. Beyond the initially listed resources, it supports scaling for Amazon DynamoDB tables and global secondary indexes, Amazon ECS services running on Fargate or EC2, Amazon ElastiCache replication groups, Amazon Neptune clusters, Amazon SageMaker endpoint variants, and custom resources via the AWS Lambda-backed scalable target. This makes it a central tool for architects and DevOps engineers in building resilient, self-optimizing cloud architectures. Typical enterprise use cases include dynamically adjusting the number of Aurora read replicas to handle database query load spikes, scaling ECS task counts during peak traffic for a microservices application, or optimizing costs by scaling down SageMaker inference endpoints during off-hours.
Related MCP Server Integrations
PostgreSQL (MCP) MCP Setup
Query and manage PostgreSQL databases directly from your AI agent. Read schemas, run queries, and manage data.
Notion API MCP Setup
The Notion API is a comprehensive RESTful interface provided by Notion, the popular all-in-one workspace platform, enabling programmatic interaction with its rich set of collaborative objects. It grants developers and automated systems the ability to read, create, update, and manage core Notion entities such as blocks (the fundamental building blocks of content like text, lists, and media), databases (structured tables with properties), pages (containers for content and databases), and comments. Typical use cases span enterprise and consumer scenarios, including automating team workflows, syncing data between Notion and other business systems (like CRM, project management, or analytics tools), building custom dashboards, generating dynamic reports, and enhancing content collaboration through programmatic updates. Organizations leverage this API to break down data silos, enforce process automation, and create tailored integrations that extend Notion's native capabilities for specific departmental or cross-functional needs.
Amazon CloudWatch Application Insights MCP Setup
Amazon CloudWatch Application Insights is a specialized observability service provided by Amazon Web Services (AWS) designed to simplify the monitoring and troubleshooting of applications, particularly those built on Microsoft IIS and .NET frameworks running on EC2 instances or within Elastic Beanstalk environments. Its core capability lies in automatically discovering application components, analyzing correlated metrics, logs, and traces to identify anomalies, and then surfacing actionable insights that pinpoint the root cause of common operational issues. By integrating seamlessly with other AWS services like CloudWatch, AWS X-Ray, and AWS Systems Manager, it provides a unified view of application health, reducing the mean time to resolution (MTTR) for performance degradations and errors. The typical use case spans enterprise environments managing distributed microservices or monolithic .NET applications, where teams need to proactively detect issues such as memory leaks, high CPU utilization, or specific application errors without manually configuring complex monitoring dashboards and alarms.
Application Auto Scaling MCP Setup
The Application Auto Scaling API, provided by Amazon Web Services (AWS), is a robust service designed to automate the scaling of computing resources for a wide array of AWS services, ensuring optimal performance, availability, and cost efficiency. Its core capability is to define policies that automatically adjust the provisioned capacity of supported resources in response to changing demand, as measured by CloudWatch metrics or predefined schedules. Beyond the initially listed resources, it supports scaling for Amazon DynamoDB tables and global secondary indexes, Amazon ECS services running on Fargate or EC2, Amazon ElastiCache replication groups, Amazon Neptune clusters, Amazon SageMaker endpoint variants, and custom resources via the AWS Lambda-backed scalable target. This makes it a central tool for architects and DevOps engineers in building resilient, self-optimizing cloud architectures. Typical enterprise use cases include dynamically adjusting the number of Aurora read replicas to handle database query load spikes, scaling ECS task counts during peak traffic for a microservices application, or optimizing costs by scaling down SageMaker inference endpoints during off-hours.
AWS Cost Explorer Service MCP Setup
The AWS Cost Explorer API, provided by Amazon Web Services, serves as the programmatic backbone for the Cost Explorer service, a powerful tool designed to help organizations visualize, understand, and manage their AWS cloud spending. At its core, this API enables developers and financial operations (FinOps) teams to move beyond the web console and directly query their cost and usage data, unlocking the ability to build custom dashboards, automated reports, and sophisticated cost management applications. Its capabilities range from retrieving high-level aggregated data, such as monthly service costs or daily usage totals, to drilling down into granular, resource-level details, including the specific write operations of a DynamoDB table or the data transfer metrics of an EC2 instance. This granular access is critical for enterprises implementing showback/chargeback models, identifying optimization opportunities, and enforcing budget guardrails across complex, multi-account AWS environments.