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.
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.
- 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
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.
One command plus a key — npm install mcp-mongodb-atlas, then supply credentials