MCP Tool to operate and integrate MongoDB Atlas projects into an AI developed project
Mcp mongodb atlas mcp server lets Claude, Cursor and other MCP clients work with MCP Mongodb Atlas directly. MCP Tool to operate and integrate MongoDB Atlas projects into an AI developed project.
Once connected, the assistant can call these 7 tools directly:
create_atlas_cluster — Create a new MongoDB Atlas cluster in an existing projectsetup_atlas_network_access — Configure network access for an Atlas projectcreate_atlas_user — Create a new database user with atlasAdmin roleget_atlas_connection_strings — Retrieve connection strings for a clusterlist_atlas_projects — List all Atlas projects accessible with the provided API keylist_atlas_clusters — List all clusters in a specific Atlas projectDebugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector:The server is distributed via npm as mcp-mongodb-atlas, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 2 environment variables: ATLAS_PUBLIC_KEY, ATLAS_PRIVATE_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. MCP Mongodb Atlas sits in that group, and the shape of its toolset — create_atlas_cluster, setup_atlas_network_access, create_atlas_user among others — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| create_atlas_cluster | Create a new MongoDB Atlas cluster in an existing project |
| setup_atlas_network_access | Configure network access for an Atlas project |
| create_atlas_user | Create a new database user with atlasAdmin role |
| get_atlas_connection_strings | Retrieve connection strings for a cluster |
| list_atlas_projects | List all Atlas projects accessible with the provided API key |
| list_atlas_clusters | List all clusters in a specific Atlas project |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector: |
{
"mcpServers": {
"mongodb-atlas": {
"command": "npx",
"args": ["-y", "mcp-mongodb-atlas"],
"env": {
"ATLAS_PUBLIC_KEY": "your-value",
"ATLAS_PRIVATE_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ATLAS_PUBLIC_KEY | Credential the server authenticates with. | Yes |
| ATLAS_PRIVATE_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.