Resources · Claude connector

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

Overview

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.

Vocabulary

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.
Connect

Set up the Claude MongoDB Atlas connector in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (21)

21 tools

Twenty-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.

When it helps
you want average basket size by country for last month, straight from the orders collection.
Watch out
some pipeline stages can output to a collection, see the limits section further down.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
your question is about a whole database rather than a single collection.
Watch out
as with the previous tool, a careless pipeline can have side effects, covered in the limits section.

Sourcemongodb.com · October 1, 2026 ↗

atlas-get-performance-advisor

Returns Atlas Performance Advisor recommendations for a cluster: suggested indexes, indexes worth dropping, slow query logs and schema advice.

When it helps
your app crawls at peak hours and you want to know which queries cost the most.
Watch out
MongoDB requires at least the Project Read Only role and an M10 or larger cluster.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you want to check which ranges a cluster already allows before adding another.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you just resumed a paused cluster and are waiting for it to be ready again.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you want to see what fired on a project before looking at one cluster in detail.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you want an inventory of clusters before touching anything.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you're preparing an access review and looking for accounts nobody uses anymore.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you work for several clients and want to confirm which organization Claude will look in first.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you're trying to find which project holds the staging cluster before reading its alerts.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you want to see which processors exist in a workspace .

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
a product search is slow and you want to confirm an index actually covers the field being queried.

Sourcemongodb.com · October 1, 2026 ↗

collection-schema

Describes a collection's schema, meaning the usual shape of its documents and their fields. Claude understands the data before querying it.

When it helps
you inherited a database from another team and have no idea yet which fields it holds.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
storage keeps climbing and you suspect the logs collection is the culprit.

Sourcemongodb.com · October 1, 2026 ↗

count

Returns the number of documents in a collection. A plain question, a single figure in return. No documents come back, only the total.

When it helps
you want to know how many documents a collection holds before running a heavier query.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you compare two databases before deciding which one to migrate first.

Sourcemongodb.com · October 1, 2026 ↗

explain

Shows how MongoDB's query optimizer runs a query: the winning plan and its execution statistics. You see why a query is slow.

When it helps
a page on your site takes seconds to load and you suspect a query that scans the whole collection.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you want every order from one specific customer.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you're new to an internal tool's database and want its map before asking anything specific.

Sourcemongodb.com · October 1, 2026 ↗

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.

When it helps
you don't know yet whether billing data lives in its own database or mixed in elsewhere.

Sourcemongodb.com · October 1, 2026 ↗

remote-atlas-connect

Opens a connection to an Atlas cluster from MongoDB's remote server. The database tools then rely on that connection.

When it helps
you switch from the staging cluster to production within the same conversation.
Watch out
the connection carries your Atlas identity, so everything your role allows comes within reach.

Sourcemongodb.com · October 1, 2026 ↗

What Claude changes (20)

20 tools

Twenty 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 rule

Configures an Atlas cluster's IP access list: the addresses and network ranges allowed to connect to it.

What Claude asks for
no source documents a confirmation specific to opening IP access; the general approval rule applies.
When it helps
a new application server has to reach the database the moment it goes live.
Watch out
MongoDB warns that an entry like 0.0.0.0/0 opens the cluster to every address.

Sourcemongodb.com · October 1, 2026 ↗

atlas-create-cluster

Approval: see the rule

Creates 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.

What Claude asks for
nothing specific is documented for creating a dedicated cluster; see the general rule below.
When it helps
you're launching a new product and want an environment isolated from everything else.
Watch out
a SHARDED cluster is single-shard only and requires M30 or higher.

Sourcemongodb.com · October 1, 2026 ↗

atlas-create-db-user

Approval: see the rule

Adds a new Atlas database user, one of the accounts that applications and people use to connect to the data.

What Claude asks for
no source describes a dedicated confirmation for new users; the default rule covers this tool.
When it helps
an application needs its own account to connect to a database.

Sourcemongodb.com · October 1, 2026 ↗

atlas-create-free-cluster

Approval: see the rule

Creates a free Atlas cluster, handy for a trial or a demo without committing any budget.

What Claude asks for
creating a free cluster has no documented approval rule of its own, so the general rule is what governs.
When it helps
you want to try out a data model idea on a separate cluster.

Sourcemongodb.com · October 1, 2026 ↗

atlas-create-project

Approval: see the rule

Creates a new Atlas project, the folder that will later hold clusters, users and access rules.

What Claude asks for
no source spells out a check for project creation; it falls back to the general rule.
When it helps
you want a separate space for a new project, with its own clusters.

Sourcemongodb.com · October 1, 2026 ↗

atlas-load-sample-dataset

Approval: see the rule

Loads a MongoDB-provided sample dataset into an Atlas cluster, so you can practice on realistic data.

What Claude asks for
loading samples comes with no documented confirmation; the default rule applies.
When it helps
you want to practice on sample data without touching your own.

Sourcemongodb.com · October 1, 2026 ↗

atlas-pause-resume-cluster

Approval: see the rule

Pauses a dedicated cluster, which makes it unreachable and stops compute costs, or resumes it later.

What Claude asks for
no source says whether Claude confirms before a pause or resume; the general rule frames it.
When it helps
an environment isn't in use right now and you want to stop its compute costs.
Watch out
free and Flex clusters can't be paused, and a pause cuts every connection.

Sourcemongodb.com · October 1, 2026 ↗

atlas-streams-build

Approval: see the rule

Creates Atlas Stream Processing pieces: a workspace, a processor, a public connection or a private networking connection.

What Claude asks for
creating a stream component has no confirmation of its own in the sources; the general rule applies.
When it helps
you want to transform an app's events continuously before storing them.
Watch out
MongoDB notes that every running processor is billed.

Sourcemongodb.com · October 1, 2026 ↗

atlas-streams-manage

Approval: see the rule

Manages an existing stream setup: starts, stops or updates a processor, edits a workspace or a connection, accepts or rejects a private connection.

What Claude asks for
no source describes a check for these state changes; refer to the default rule.
When it helps
a processor is burning resources and you want it stopped while you fix its logic.

Sourcemongodb.com · October 1, 2026 ↗

atlas-streams-teardown

Approval: see the rule

Deletes an Atlas Stream Processing workspace, processor or connection.

What Claude asks for
deleting a stream component has no documented approval rule; the general rule is in charge.
When it helps
a pilot project wrapped up and you no longer want to pay for its processors.

Sourcemongodb.com · October 1, 2026 ↗

atlas-upgrade-cluster

Approval: see the rule

Moves a cluster up a tier: free to Flex or to a dedicated instance, or resizes a dedicated cluster and its autoscaling settings.

What Claude asks for
nothing in the sources points to an upgrade-specific confirmation; the general rule governs.
When it helps
your prototype found its users and the free cluster is maxed out.
Watch out
the supported moves are from free to Flex, from free to M10, and from Flex to M10.

Sourcemongodb.com · October 1, 2026 ↗

create-collection

Approval: see the rule

Adds a brand-new, empty collection to a database, ready to receive documents.

What Claude asks for
no source describes a confirmation specific to collection creation; the default rule applies.
When it helps
you're adding a customer reviews module and those reviews need somewhere to live.

Sourcemongodb.com · October 1, 2026 ↗

create-index

Approval: see the rule

Creates an index on a collection, including vector or full-text search indexes, to speed up certain queries.

What Claude asks for
index creation has no documented check, so the general approval rule covers it.
When it helps
the Performance Advisor suggested an index and you want to apply it right away.

Sourcemongodb.com · October 1, 2026 ↗

delete-many

Approval: see the rule

Removes every document in a collection that matches a filter, in a single operation.

What Claude asks for
no source guarantees a confirmation before deleting documents; the general rule frames it.
When it helps
you need to wipe the test accounts created during a QA campaign.

Sourcemongodb.com · October 1, 2026 ↗

drop-collection

Approval: see the rule

Deletes an entire collection from a database, along with all of its documents.

What Claude asks for
nothing specific is documented for dropping a collection; see the default rule.
When it helps
an old import collection is no longer used and clutters the database.

Sourcemongodb.com · October 1, 2026 ↗

drop-database

Approval: see the rule

Wipes out a whole database, collections included, in one call.

What Claude asks for
no source says whether Claude confirms before dropping a database; only the general rule applies.
When it helps
a demo environment is shutting down and its database should go with it.
Watch out
Claude acts with your Atlas role: if your role can drop a database, so can it.

Sourcemongodb.com · October 1, 2026 ↗

drop-index

Approval: see the rule

Removes an index from a collection, including vector or full-text search indexes.

What Claude asks for
index removal has no confirmation documented in the sources; the default rule applies.
When it helps
the Performance Advisor flags an unused index that slows down inserts.

Sourcemongodb.com · October 1, 2026 ↗

insert-many

Approval: see the rule

Adds several documents to a collection in one go.

What Claude asks for
no source describes a check specific to inserts; it's the general approval rule.
When it helps
you want to load a product list from a supplier without writing a script.

Sourcemongodb.com · October 1, 2026 ↗

rename-collection

Approval: see the rule

Changes the name of an existing collection without touching its documents.

What Claude asks for
renaming has no documented approval rule; refer to the general rule.
When it helps
a collection still carries an old project name and keeps confusing people.

Sourcemongodb.com · October 1, 2026 ↗

update-many

Approval: see the rule

Modifies every document in a collection that matches a filter, all at once.

What Claude asks for
no source guarantees a confirmation before a bulk update; the general rule applies.
When it helps
you need to mark every product from a discontinued brand as out of stock.

Sourcemongodb.com · October 1, 2026 ↗

Approvals

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.

Plans

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.

Limits

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

Need help connecting MongoDB Atlas to Claude?

A person reads every message.

FAQ

Claude MongoDB Atlas connector: common questions

01What can Claude do with the MongoDB Atlas connector?
Claude can query your data and administer your Atlas infrastructure from the chat. Its 41 tools cover finding, counting and aggregating documents, analyzing slow queries, reading schemas and indexes, and taking inventory of organizations, projects, clusters, alerts and users. They also cover creating clusters, indexes and collections, managing IP access and running stream processors. Everything goes through your Atlas identity and the role attached to it. It can also connect to a cluster through MongoDB's remote server.
02Can Claude change or delete data in MongoDB Atlas?
Yes, 20 tools change something. Claude can insert, update and delete documents, create, rename or drop collections, drop an entire database, and create or remove indexes. On the infrastructure side it creates projects and clusters, pauses or upgrades a cluster, creates database users, opens IP access and manages streams. MongoDB also notes that two aggregation tools labeled as reads can write a collection. And every running stream processor is billed, per MongoDB.
03Does Claude ask before changing my Atlas data?
By default, Claude asks for your approval before each action it takes on an account on your behalf. MongoDB adds its own confirmation prompt for some tools, but it only appears if the client supports it, and the publisher advises not to count on it before a risky operation. On Team and Enterprise, owners can also close writes for the whole organization. And Claude stays bounded by the Atlas role of the connected identity.
04Which Claude plans support the MongoDB Atlas connector?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them on Team and Enterprise. For the current status, check the MongoDB Atlas sheet in the official directory from your own account, the only place that reflects it.
05Does Claude see all of our MongoDB Atlas databases?
Claude sees everything your Atlas role allows, and nothing more. It acts under your identity, and MongoDB states you can't delegate only part of your permissions: if your role is broad, Claude ends up with all of it. At the organization level, an owner has to enable the AI Clients setting first, and every action stays logged under your name. Access also ends after 7 days of inactivity, or 30 days after you granted it.
06Why does Claude need to reconnect to MongoDB Atlas after a few weeks?
Because MongoDB limits how long an AI client's access lasts. It ends after 7 days without use, or 30 days after authorization no matter what. You then authorize again, through the same Atlas screen that ends with the Authorize button. In the meantime, Atlas attributes every action the AI client took to you in its audit log. You can also revoke access at any time from the Atlas user interface.
07Claude or an automation tool for MongoDB Atlas?
They do different jobs. Claude works in a conversation: you ask, it queries, explains, fixes an index or creates a cluster, and nothing runs outside the conversation. Nothing reacts on its own to an alert or to new documents arriving. An automation tool exists to run a task in the background on an event or a schedule. One answers a request made in the moment, the other runs a planned task: they are not two versions of the same service.