Aggregate
Run an aggregation against a MongoDB collection
ActionTry it
Integrate MongoDB MCP
with your AI CRM
MongoDB MCP lets authorized agents explore and manage MongoDB Atlas resources, databases, collections, documents, indexes, performance data, and MongoDB knowledge sources.
Explore Triggers and Actions
Aggregate-db
Run an aggregation against a MongoDB database
ActionTry it
Atlas-create-access-list
Allow Ip/CIDR ranges to access your MongoDB Atlas clusters.
ActionTry it
Atlas-create-cluster
Create a MongoDB Atlas cluster (M10–M80, replica set or single shard, single or multi-region). Compute autoscaling is enabled by default: min instance size is set to the selected instance size, max is set two tiers above. Disk autoscaling is always enabled. For encryption at rest, the CMK provider must already have a valid configuration in the Atlas project. The tool returns immediately, use the atlas-inspect-cluster tool to poll the cluster state for readiness (state: IDLE). Connection strings are unavailable until the cluster reaches IDLE state. Note to LLM: Omit instance size unless specified by the user. If provider and regions are not already known, ask for both together in a single question before calling this tool. Common, non-exhaustive region default mappings by provider: AWS: "East Coast"/"Virginia"/"US East" → US_EAST_1, "Ohio" → US_EAST_2, "California"/"West Coast" → US_WEST_2, "Southeast Asia"/"APAC"/"Singapore" → AP_SOUTHEAST_1, "Europe"/"EU"/"Ireland" → EU_WEST_1. GCP: "Central US" → CENTRAL_US, "Western US" → WESTERN_US, "Southeast Asia"/"APAC" → SOUTHEASTERN_ASIA_PACIFIC, "Europe"/"EU" → WESTERN_EUROPE. AZURE: "East US" → US_EAST_2, "West US" → US_WEST_2, "Europe North" → EUROPE_NORTH, "Europe West" → EUROPE_WEST. Default recommendation: AWS US_EAST_1. User-specified regions not present in the mapping MUST be respected, rely on the tool to surface errors if a region is not supported.
ActionTry it
Atlas-create-db-user
Create an MongoDB Atlas database user
ActionTry it
Atlas-create-free-cluster
Create a free MongoDB Atlas cluster
ActionTry it
Atlas-create-project
Create a MongoDB Atlas project
ActionTry it
Atlas-get-performance-advisor
Get MongoDB Atlas performance advisor recommendations and suggestions, which includes the operations: suggested indexes, drop index suggestions, schema suggestions, and a sample of the most recent (max 50) slow query logs
ActionTry it
Atlas-inspect-access-list
Inspect Ip/CIDR ranges with access to your MongoDB Atlas clusters.
ActionTry it
Atlas-inspect-cluster
Inspect metadata of a MongoDB Atlas cluster
ActionTry it
Atlas-list-alerts
List triggered alerts for a MongoDB Atlas project. These are alerts Atlas has raised, not the alert configurations that define them. Defaults to OPEN alerts; set status to TRACKING or CLOSED to see others.
ActionTry it
Atlas-list-clusters
List MongoDB Atlas clusters
ActionTry it
Atlas-list-db-users
List MongoDB Atlas database users
ActionTry it
Atlas-list-orgs
List MongoDB Atlas organizations
ActionTry it
Atlas-list-projects
List MongoDB Atlas projects.
ActionTry it
Atlas-load-sample-dataset
Load a MongoDB sample dataset into an Atlas cluster, or check the status of a previously-initiated load. To start a new load, provide `clusterName` — the load runs asynchronously and the response includes a `jobId` and initial state. To check progress, call this tool again with `jobId` (sample dataset loads typically take 1–5 minutes). State can be WORKING, COMPLETED, or FAILED.
ActionTry it
Atlas-pause-resume-cluster
Pause or resume a dedicated (M10+) MongoDB Atlas cluster (Free and Flex clusters cannot be paused). Pause: paused clusters are unavailable for connections and do not incur compute costs. If the cluster being paused is the current active connection, it will be automatically disconnected. Returns an error if the cluster is already paused or not in a pausable state (must be IDLE). Resume: the cluster will not be immediately available after resuming. Use the atlas-inspect-cluster tool to poll the cluster state for readiness (state: IDLE). If the cluster is not paused, resuming it is a no-op.
ActionTry it
Atlas-streams-build
Create Atlas Stream Processing resources. Use this tool for 'set up a Kafka pipeline', 'create a workspace', 'add a connection', or 'deploy a processor'. Use resource='workspace' to create a new workspace (specify cloud provider, region, and tier). Use resource='connection' to add a data source or sink to an existing workspace. Use resource='processor' to deploy a stream processor with a pipeline. Use resource='privatelink' to set up private networking. Typical workflow: create workspace → add connections → deploy processor.
ActionTry it
Atlas-streams-discover
Discover and inspect Atlas Stream Processing resources. Also use for 'why is my processor failing', 'what workspaces do I have', 'show processor stats', or 'check processor health'. Use 'list-workspaces' to see all workspaces in a project. Use inspect actions for details on a specific resource. Use 'diagnose-processor' for a combined health report including state, stats, connection health, and recent errors. Use 'get-networking' for PrivateLink and account details.
ActionTry it
Atlas-streams-manage
Manage Atlas Stream Processing resources: start/stop processors, modify pipelines, update configurations. Also use for 'change the pipeline', 'scale up my processor', or 'update my workspace tier'. Common workflow: action='stop-processor' → action='modify-processor' → action='start-processor'. Use `atlas-streams-discover` with action 'inspect-processor' to check state before managing.
ActionTry it
Atlas-streams-teardown
Delete Atlas Stream Processing resources. Also use for 'remove my workspace', 'disconnect a source', 'delete all processors', or 'clean up my streams environment'. Performs basic safety checks before deletion: summarizes counts of processors and connections, highlights connections referenced by processors where possible, and surfaces API errors if processors are still running when deletion is attempted. Use `atlas-streams-discover` to review resources before deleting.
ActionTry it
Atlas-upgrade-cluster
Upgrade a MongoDB Atlas cluster tier. Upgrades Free (M0) clusters to Flex or M10 Dedicated, or Flex clusters to M10 Dedicated. The upgrade path is determined automatically from the current tier unless overridden with targetTier. Note to LLM: If provider and region are not already known, ask for both together in a single question before calling this tool. Common region mappings by provider (default recommendation: AWS US_EAST_1): AWS: "East Coast"/"Virginia"/"US East" → US_EAST_1, "Ohio" → US_EAST_2, "California"/"West Coast" → US_WEST_2, "Southeast Asia"/"APAC"/"Singapore" → AP_SOUTHEAST_1, "Europe"/"EU"/"Ireland" → EU_WEST_1. GCP: "Central US" → CENTRAL_US, "Western US" → WESTERN_US, "Southeast Asia"/"APAC" → SOUTHEASTERN_ASIA_PACIFIC, "Europe"/"EU" → WESTERN_EUROPE. AZURE: "East US" → US_EAST_2, "West US" → US_WEST_2, "Europe"/"EU" → EUROPE_NORTH.
ActionTry it
Collection-indexes
Describe the indexes for a collection
ActionTry it
Collection-schema
Describe the schema for a collection
ActionTry it
Collection-storage-size
Gets the size of the collection
ActionTry it
Count
Gets the number of documents in a MongoDB collection using db.collection.count() and query as an optional filter parameter
ActionTry it
Create-collection
Creates a new collection in a database. If the database doesn't exist, it will be created automatically.
ActionTry it
Create-index
Create an index for a collection
ActionTry it
Db-stats
Returns statistics that reflect the use state of a single database
ActionTry it
Delete-many
Removes all documents that match the filter from a MongoDB collection
ActionTry it
Drop-collection
Removes a collection or view from the database. The method also removes any indexes associated with the dropped collection.
ActionTry it
Drop-database
Removes the specified database, deleting the associated data files
ActionTry it
Drop-index
Drop an index for the provided database and collection.
ActionTry it
Explain
Returns statistics describing the execution of the winning plan chosen by the query optimizer for the evaluated method
ActionTry it
Find
Run a find query against a MongoDB collection
ActionTry it
Insert-many
Insert an array of documents into a MongoDB collection. If the list of documents is above com.mongodb/maxRequestPayloadBytes, consider inserting them in batches.
ActionTry it
List-collections
List all collections for a given database
ActionTry it
List-databases
List all databases for a MongoDB connection
ActionTry it
Remote-atlas-connect
Connect to MongoDB Atlas cluster
ActionTry it
Rename-collection
Renames a collection in a MongoDB database
ActionTry it
Update-many
Updates all documents that match the specified filter for a collection. If the list of documents is above com.mongodb/maxRequestPayloadBytes, consider updating them in batches.
ActionTry it
How the MongoDB MCP integration works
The MongoDB MCP integration connects your Dench AI CRM directly to MongoDB MCP, so agents can read and act on your MongoDB MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
41 actions are available for agents to invoke on your behalf. Every call runs through MongoDB MCP's own authorization, scoped to the account you connect.
Set up MongoDB MCP in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find MongoDB MCP and click Connect — you'll authorize access through MongoDB MCP's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use MongoDB MCP in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the MongoDB MCP integration work with Dench?
The Dench MongoDB MCP integration connects your AI CRM to MongoDB MCP, so AI agents can work with your MongoDB MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with MongoDB MCP via Dench?
The MongoDB MCP integration currently exposes 41 actions, including Aggregate, Aggregate-db, Atlas-create-access-list, Atlas-create-cluster, Atlas-create-db-user, and Atlas-create-free-cluster. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect MongoDB MCP to Dench?
No. You connect MongoDB MCP from your Dench workspace using MongoDB MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the MongoDB MCP integration secure?
Connections are authorized through MongoDB MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the MongoDB MCP connection from your workspace settings at any time.