MongoDB MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

atlas-list-db-users

Read-only

List MongoDB Atlas database users for a specific project by providing its project ID. Use this to retrieve user accounts and their roles.

Instructions

List MongoDB Atlas database users

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes	Atlas project ID to filter DB users

Output Schema

TableJSON Schema

Name	Required	Description	Default
`users`	Yes
`projectId`	Yes
`totalCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Aug 4, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedv1.14.0Jul 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "projectId": {
+      "type": "string"
+    },
+    "totalCount": {
+      "type": "number"
+    },
+    "users": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "roles": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "collectionName": {
+                  "type": "string"
+                },
+                "databaseName": {
+                  "type": "string"
+                },
+                "roleName": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "roleName",
+                "databaseName"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "scopes": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "name": {
+                  "type": "string"
+                },
+                "type": {
+                  "enum": [
+                    "CLUSTER",
+                    "DATA_LAKE",
+                    "STREAM"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "name"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "username": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "username",
+          "roles",
+          "scopes"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "projectId",
+    "users",
+    "totalCount"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.11.0May 22, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
Addedv1.0.0Jan 3, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no additional behavioral context such as pagination, return format, authentication needs, or rate limits. With annotations covering the safety profile, a neutral score is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no wasted words. It is immediately clear and front-loaded, making it easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and an output schema provided. The description is minimal but adequate when combined with the annotations and schema. It could explicitly mention that the listing is scoped to a project, but the schema already communicates this, so the overall context is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema fully documents projectId with a description and validation pattern, giving 100% schema coverage. The description does not mention parameters, but the schema carries the burden. Baseline 3 is appropriate since the description does not add extra meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and the resource ('MongoDB Atlas database users'). It distinguishes itself from sibling tools like atlas-list-clusters, atlas-list-projects, and atlas-list-alerts by specifying the exact entity being listed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no context about the required projectId. It merely states the action without any usage policy, leaving the agent to infer the appropriate context from the tool name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.