create_atlas_cluster
Creates a new Atlas cluster in an existing Atlas project.
LABSCO SUMMARY
The four steps between an empty Atlas project and a working connection string.
Creating a cluster, adding a user, opening network access and fetching the connection string is the sequence everyone does by hand in the Atlas interface, collapsed into one conversation. It is scoped tightly to that path — there is nothing here for querying data once the cluster is up. This is the community-maintained Atlas server; MongoDB publishes an official one separately.
What it is
A server over the Atlas administration API covering the setup half of Atlas: it lists your projects and clusters, creates a cluster in an existing project, adds a database user, opens network access, and hands back the connection strings.
What you get
- Every Atlas project the API key can reach, and the clusters inside one
- A new cluster created in an existing project
- A database user created with the admin role
- Network access configured from a list of IP addresses or CIDR blocks
- The connection strings for a cluster, ready to paste into an application
Requirements
An Atlas API key pair — public and private — created under Access Manager, supplied as environment settings or as launch arguments. Runs under Node from the published package.
Setup effort
One command plus a key — npm install mcp-mongodb-atlas, then supply credentials
USE CASES
01
Standing up a cluster for a new project
Find the project the key can reach, then create the cluster inside it without opening the console.
02
Getting an application connected
Create the database user, open network access for the addresses that need it, and read back the connection strings.
03
Checking what already exists before you create anything
List the projects and the clusters in the one you care about, so you do not duplicate something that is already running.
04
Letting a new address through
Add the IP address or CIDR block to the project's network access list in one call.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_atlas_user
Creates a new database user for an existing Atlas project. User will have atlasAdmin role.
get_atlas_connection_strings
Retrieves connection strings for a cluster in an existing Atlas project.
list_atlas_clusters
Lists all clusters in an Atlas project.
list_atlas_projects
Lists all Atlas projects that the API key has access to.
setup_atlas_network_access
Sets up network access for an existing Atlas project. Accepts list of IP addresses or CIDR blocks.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. create_atlas_user grants atlasAdmin, create_atlas_cluster provisions billable infrastructure, and setup_atlas_network_access opens access to an IP range. Nothing queries data inside a cluster.
Requires
- npx on PATH
- ATLAS_PUBLIC_KEY in your environment
- ATLAS_PRIVATE_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install mcp-mongodb-atlasMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · TERMINAL
npx mcp-mongodb-atlas "<YOUR_ATLAS_PUBLIC_KEY>" "<YOUR_ATLAS_PRIVATE_KEY>"Cline, Cursor
JSON
{
"mcpServers": {
"atlas": {
"command": "npx",
"args": [
"mcp-mongodb-atlas"
],
"env": {
"ATLAS_PUBLIC_KEY": "<YOUR_ATLAS_PUBLIC_KEY>",
"ATLAS_PRIVATE_KEY": "<YOUR_ATLAS_PRIVATE_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"atlas": {
"command": "npx",
"args": [
"mcp-mongodb-atlas"
],
"env": {
"ATLAS_PUBLIC_KEY": "<YOUR_ATLAS_PUBLIC_KEY>",
"ATLAS_PRIVATE_KEY": "<YOUR_ATLAS_PRIVATE_KEY>"
}
}
}
}
