MongoDB Atlas MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_atlas_clusterC | Creates a new Atlas cluster in an existing Atlas project. |
| setup_atlas_network_accessC | Sets up network access for an existing Atlas project. Accepts list of IP addresses or CIDR blocks. |
| create_atlas_userB | Creates a new database user for an existing Atlas project. User will have atlasAdmin role. |
| get_atlas_connection_stringsC | Retrieves connection strings for a cluster in an existing Atlas project. |
| list_atlas_projectsB | Lists all Atlas projects that the API key has access to. |
| list_atlas_clustersC | Lists all clusters in an Atlas project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting specific Atlas resources: clusters, users, connection strings, projects, and network access. There is no overlap in functionality, making it easy for an agent to select the correct tool for any given task.
All tools follow a consistent verb_noun pattern with 'atlas' as a prefix (e.g., create_atlas_cluster, list_atlas_projects). The naming is uniform and predictable, using snake_case throughout without any deviations.
With 6 tools, the count is reasonable for managing MongoDB Atlas resources, covering key operations like creation, listing, and setup. It is slightly lean but sufficient for core tasks, though additional tools for updates or deletions could enhance coverage.
The tools provide good coverage for core Atlas operations, including creation and listing of clusters and projects, user management, and network setup. However, there are minor gaps, such as missing update or delete operations for clusters and users, which agents might need to work around.