- Home
- Resources
- Integrations
- MongoDB Atlas
Claude MongoDB Atlas connectorWhat Claude can do in your MongoDB Atlas account.
The Claude MongoDB Atlas connector exposes 41 tools. 21 read your clusters and data, 20 change something, 0 undocumented. Queries, indexes, clusters, access, streams: here's what Claude reads, what it modifies, and who can stop it.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your Atlas work
MongoDB Atlas hosts your databases in the cloud. With this connector you describe what you need in plain English and Claude handles it: it queries documents, explains why a query is slow, lists alerts or spins up a cluster. It acts under your Atlas identity, so with exactly the rights your role grants, no more and no less.
Answer a question about the data. find returns the documents that match your query, while count and aggregate put numbers and groupings on it.
Diagnose a slowdown. explain shows a query's execution plan, and atlas-get-performance-advisor brings suggested indexes and slow query logs. create-index then applies the fix.
Run the infrastructure. Claude lists projects and clusters, creates a cluster, pauses it, manages database users and the IP access list, and drives Atlas Stream Processing's continuous data pipelines.
What Claude won't do: it doesn't watch anything in the background, nothing starts when an alert fires. It never exceeds your Atlas role, and you can't hand it only part of your rights. The labels saying whether a tool reads or writes are advisory, as MongoDB itself points out. A scheduled job is a task for an automation tool, a different line of work, collected on the Integrations hub.
Five words before you start
Learn these before you scroll through all 41 tools.
- Connector
- The link you set up one time between Claude and an account you already have, so Claude can work with it while it answers.
- Tool
- A single named capability the connector gives Claude. Claude decides which ones to call, and the directory sheet lists each by name.
- Authorization
- Atlas's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and revocable from Atlas.
- Approval
- The confirmation Claude waits for before it completes an action that changes your account, shown in the chat when it matters.
- MCP
- The open standard connectors are built on. It's what lets an assistant like Claude talk to an outside service such as Atlas.
Set up the Claude MongoDB Atlas connector in three steps
- 01
Find MongoDB Atlas
In Claude's settings, open Customize then Connectors and locate MongoDB Atlas in the list. On a Team or Enterprise workspace, an Owner or Primary Owner first has to enable the connector for the organization.
- 02
Start the connection
Click Connect on its row, then sign in to Atlas in the window MongoDB opens itself and complete its guided flow. If the link breaks one day, use Disconnect and reconnect.
- 03
Review the authorization
Read Atlas's screen before you click Authorize. The service, not Claude, decides what the access covers. You can revoke that access at any time from the Atlas UI.
All 41 MongoDB Atlas tools, sorted by what they do
MongoDB Atlas gives Claude 41 tools: 21 that read your account, 20 that change something in it.
Two groups: what Claude reads and what it changes. Names stay exactly as Claude shows them.
- 21 read
- 20 write
Tools index
- aggregate
- aggregate-db
- atlas-get-performance-advisor
- atlas-inspect-access-list
- atlas-inspect-cluster
- atlas-list-alerts
- atlas-list-clusters
- atlas-list-db-users
- atlas-list-orgs
- atlas-list-projects
- atlas-streams-discover
- collection-indexes
- collection-schema
- collection-storage-size
- count
- db-stats
- explain
- find
- list-collections
- list-databases
- remote-atlas-connect
- atlas-create-access-list
- atlas-create-cluster
- atlas-create-db-user
- atlas-create-free-cluster
- atlas-create-project
- atlas-load-sample-dataset
- atlas-pause-resume-cluster
- atlas-streams-build
- atlas-streams-manage
- atlas-streams-teardown
- atlas-upgrade-cluster
- create-collection
- create-index
- delete-many
- drop-collection
- drop-database
- drop-index
- insert-many
- rename-collection
- update-many
What Claude reads (21)
21 toolsTwenty-one tools that query your data or describe your Atlas infrastructure.
aggregate
Runs a MongoDB aggregation pipeline on a collection: a chain of stages that filter, group and compute, so you get a summary table instead of a pile of raw documents.
aggregate-db
Runs the same kind of pipeline across a whole database rather than a single collection, for questions that span more than one collection.
atlas-get-performance-advisor
Returns Atlas Performance Advisor recommendations for a cluster: suggested indexes, indexes worth dropping, slow query logs and schema advice.
Project Read Only role and an M10 or larger cluster.atlas-inspect-access-list
Shows which IP addresses and network ranges are allowed to reach an Atlas cluster, so you know exactly who can knock on the door.
atlas-inspect-cluster
Returns details on one specific Atlas cluster, including its state. MongoDB also uses it to track a cluster until it's available again after a pause.
atlas-list-alerts
Pulls the list of alerts for an Atlas project, so you can see at a glance what fired and on which cluster. Handy for a quick status check.
atlas-list-clusters
Returns the list of Atlas clusters, meaning the groups of servers that host your databases, so you know what's running and where. It's the natural starting point before inspecting one.
atlas-list-db-users
Displays the database users defined in Atlas, the accounts that apps and people use to connect to your data. Useful when access hygiene is on the agenda.
atlas-list-orgs
Lists the Atlas organizations your identity can reach, the top level of MongoDB's hierarchy. Useful as soon as one login spans several companies or business units.
atlas-list-projects
Returns Atlas projects, the folders that group clusters, users and access rules inside an organization. It helps you pin down the right scope before any deeper question.
atlas-streams-discover
Describes the parts of Atlas Stream Processing, the service for processing data continuously: workspaces, processors, public or private connections. Nothing is started or stopped, it only describes.
collection-indexes
Details a collection's indexes, including vector and full-text search indexes, the structures that make queries faster. A missing index often explains a slow page.
collection-schema
Describes a collection's schema, meaning the usual shape of its documents and their fields. Claude understands the data before querying it.
collection-storage-size
Returns a collection's size in megabytes, so you can spot what's taking up the most room on a cluster. Good for spotting which collections have grown far beyond the rest.
count
Returns the number of documents in a collection. A plain question, a single figure in return. No documents come back, only the total.
db-stats
Returns statistics for a database: volume, object count and other health indicators worth keeping an eye on. Think of it as a health check for one database at a time.
explain
Shows how MongoDB's query optimizer runs a query: the winning plan and its execution statistics. You see why a query is slow.
find
Runs a standard query against a collection and returns the documents that match your criteria. It's MongoDB's basic query, labeled as a read: no document is changed along the way.
list-collections
Lists the collections in a database, MongoDB's equivalent of tables, so you know where to look. Each collection is a group of related documents.
list-databases
Returns every database available through the current connection. From there, Claude knows which database to dig into next. The list depends on the connection opened to the cluster by the connect tool.
remote-atlas-connect
Opens a connection to an Atlas cluster from MongoDB's remote server. The database tools then rely on that connection.
What Claude changes (20)
20 toolsTwenty tools that create, modify or delete. No source details a per-tool confirmation, so the general rule below applies.
atlas-create-access-list
Approval: see the ruleConfigures an Atlas cluster's IP access list: the addresses and network ranges allowed to connect to it.
0.0.0.0/0 opens the cluster to every address.atlas-create-cluster
Approval: see the ruleCreates a dedicated Atlas cluster with instance sizes from M10 to M80, as a replica set or single shard, across one to three regions in priority order.
SHARDED cluster is single-shard only and requires M30 or higher.atlas-create-db-user
Approval: see the ruleAdds a new Atlas database user, one of the accounts that applications and people use to connect to the data.
atlas-create-free-cluster
Approval: see the ruleCreates a free Atlas cluster, handy for a trial or a demo without committing any budget.
atlas-create-project
Approval: see the ruleCreates a new Atlas project, the folder that will later hold clusters, users and access rules.
atlas-load-sample-dataset
Approval: see the ruleLoads a MongoDB-provided sample dataset into an Atlas cluster, so you can practice on realistic data.
atlas-pause-resume-cluster
Approval: see the rulePauses a dedicated cluster, which makes it unreachable and stops compute costs, or resumes it later.
atlas-streams-build
Approval: see the ruleCreates Atlas Stream Processing pieces: a workspace, a processor, a public connection or a private networking connection.
atlas-streams-manage
Approval: see the ruleManages an existing stream setup: starts, stops or updates a processor, edits a workspace or a connection, accepts or rejects a private connection.
atlas-streams-teardown
Approval: see the ruleDeletes an Atlas Stream Processing workspace, processor or connection.
atlas-upgrade-cluster
Approval: see the ruleMoves a cluster up a tier: free to Flex or to a dedicated instance, or resizes a dedicated cluster and its autoscaling settings.
M10, and from Flex to M10.create-collection
Approval: see the ruleAdds a brand-new, empty collection to a database, ready to receive documents.
create-index
Approval: see the ruleCreates an index on a collection, including vector or full-text search indexes, to speed up certain queries.
delete-many
Approval: see the ruleRemoves every document in a collection that matches a filter, in a single operation.
drop-collection
Approval: see the ruleDeletes an entire collection from a database, along with all of its documents.
drop-database
Approval: see the ruleWipes out a whole database, collections included, in one call.
drop-index
Approval: see the ruleRemoves an index from a collection, including vector or full-text search indexes.
insert-many
Approval: see the ruleAdds several documents to a collection in one go.
rename-collection
Approval: see the ruleChanges the name of an existing collection without touching its documents.
update-many
Approval: see the ruleModifies every document in a collection that matches a filter, all at once.
What Claude checks with you first
By default, Claude stops and asks before every action it takes on an account for you. With 20 write tools, several of them deletions, that rule matters.
MongoDB also describes its own confirmation prompt for some tools, without naming which. It only shows up if the client supports it, and MongoDB warns against assuming it will appear before a risky operation. On Team and Enterprise, owners decide whether members may let some actions through, and can close writes for everyone. And Claude acts under your Atlas role, never beyond it. MongoDB calls its prompt elicitation.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. Connector by connector, that information isn't published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization. For MongoDB Atlas's current status, its sheet in the official directory is the reference to check.
Where the MongoDB Atlas connector stops
A connector isn't an automation. Claude calls these tools while it answers you, and nothing fires when an Atlas alert goes off.
Only the publisher documents this connector: neither Claude's help center nor Anthropic's docs have a page for it. The read or write labels MongoDB puts on its tools are advisory: they don't authorize or block anything, and a client can ignore them. The directory badge isn't a security audit either, and Anthropic doesn't vouch for a publisher's tools. Connect only publishers you know. Every action the AI client takes is attributed to you in Atlas's audit log.
Need help connecting MongoDB Atlas to Claude?
A person reads every message.