MongoDB
Lets an agent access MongoDB databases and use MongoDB Atlas tools. Summary written by AI Index.
The registry’s description: MongoDB Model Context Protocol Server
Add to your client
Add the MongoDB MCP server to Claude Code
Run the command
claude mcp add mongodb -- npx -y mongodb-mcp-serverFill in the values ↓
Check it’s connected
Add the MongoDB MCP server to Cursor
Open mcp.json· Where the file is:
~/.cursor/mcp.json,.cursor/mcp.jsonPaste the server entry
{ "mcpServers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ] } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to VS Code
Open mcp.json· Where the file is:
.vscode/mcp.jsonPaste the server entry
{ "servers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ] } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to Codex
Run the command
codex mcp add mongodb -- npx -y mongodb-mcp-serverFill in the values ↓
Check it’s connected
Add the MongoDB MCP server to Devin Desktop
Open mcp_config.json· Where the file is:
~/.config/devin/mcp_config.json,%APPDATA%\devin\mcp_config.jsonPaste the server entry
{ "mcpServers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ] } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to Gemini CLI
Open settings.json· Where the file is:
~/.gemini/settings.json,.gemini/settings.jsonPaste the server entry
{ "mcpServers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ] } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to GitHub Copilot
Run the command
copilot mcp add mongodb -- npx -y mongodb-mcp-serverFill in the values ↓
Check it’s connected
Add the MongoDB MCP server to Cline
Open cline_mcp_settings.json· Where the file is:
~/.cline/data/settings/cline_mcp_settings.jsonPaste the server entry
{ "mcpServers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ] } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to Kiro
Open mcp.json· Where the file is:
.kiro/settings/mcp.json,~/.kiro/settings/mcp.jsonPaste the server entry
{ "mcpServers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ] } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to Zed
Open settings.json
Paste the server entry
{ "context_servers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ], "env": {} } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to OpenCode
Open opencode.json· Where the file is:
~/.config/opencode/opencode.json,opencode.jsonPaste the server entry
{ "$schema": "https://opencode.ai/config.json", "mcp": { "mongodb": { "type": "local", "command": [ "npx", "-y", "mongodb-mcp-server" ], "enabled": true } } }Fill in the values ↓
Check it’s connected
Add the MongoDB MCP server to JetBrains AI Assistant
Open JetBrains AI Assistant’s MCP config
- Open Settings | Tools | AI Assistant | Model Context Protocol (MCP).
- Choose Add.
Paste the server entry
{ "mcpServers": { "mongodb": { "command": "npx", "args": [ "-y", "mongodb-mcp-server" ] } } }Fill in the values ↓
Check it’s connected
If the file already has servers, add the entry inside the existing object. To check it’s connected, restart or reload the client and look for mongodb in its list of MCP servers. A server that needs sign-in opens it on first use.
What you fill in
Required values appear as <NAME> placeholders in the snippets; add optional ones the same way. Descriptions are the server’s registry entry’s.
<MDB_MCP_AGGREGATION_COUNT_MAX_TIME_MS_CAP>Environment variable OptionalDeprecated. Use `aggregationCountTimeoutMs` instead.
<MDB_MCP_AGGREGATION_COUNT_TIMEOUT_MS>Environment variable OptionalThe maximum time in milliseconds for the count phase of aggregation operations. This is used to limit the time spent counting documents when determining if results were capped.
<MDB_MCP_ALLOW_REQUEST_OVERRIDES>Environment variable OptionalWhen set to true, allows configuration values to be overridden via request headers and query parameters.
<MDB_MCP_API_CLIENT_ID>Environment variable Optional · SecretAtlas API client ID for authentication. Required for running Atlas tools.
<MDB_MCP_API_CLIENT_SECRET>Environment variable Optional · SecretAtlas API client secret for authentication. Required for running Atlas tools.
<MDB_MCP_ASSISTANT_BASE_URL>Environment variable OptionalBase URL for the MongoDB Assistant API.
<MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS>Environment variable OptionalTime in milliseconds that temporary database users created when connecting to MongoDB Atlas clusters will remain active before being automatically deleted.
<MDB_MCP_CONFIRMATION_REQUIRED_TOOLS>Environment variable OptionalComma separated values of tool names that require user confirmation before execution. Requires the client to support elicitation.
<MDB_MCP_CONNECTION_IDLE_TIMEOUT_MS>Environment variable OptionalMilliseconds a MongoDB connection may stay unused (no tool call touching it) before it is closed to release the underlying connection pool and its server-side state. Applied per connection regardless of its connection scope; the preconfigured connection is excluded, and the reaper runs on this cadence. Set to 0 to disable reaping; must not be negative.
<MDB_MCP_CONNECTION_SCOPE>Environment variable OptionalVisibility scope for MongoDB connections created at runtime. With 'session' (the default), each MCP session only sees the connections it created (plus the shared 'preconfigured' one) and they are closed when the session ends. With 'global', connections are shared across all sessions and survive session rotation. Deprecated: the MCP protocol is moving to sessionless, so this option will soon be removed and the connection scope will default to 'global'. For shared-server use cases, use the Atlas-Managed MCP server or build an authenticated library using the @mongodb-js/mcp-cli package. Note: on the sessionless (2026-07-28) HTTP path, a request without an mcp-session-id falls back to the shared ('global') scope so it can still persist connections across requests; the legacy sessionful path always carries a server-issued session.
<MDB_MCP_CONNECTION_STRING>Environment variable Optional · SecretMongoDB connection string for direct database connections, exposed under the connectionId "preconfigured". Optional, if not set, you'll need to call the connect tool before interacting with MongoDB data. Deprecated: prefer the "preconfigured" entry of connectionStrings.
<MDB_MCP_CONNECTION_STRINGS>Environment variable Optional · SecretMongoDB connection strings keyed by name, as a JSON object (e.g. {"preconfigured": "mongodb://...", "analytics": "mongodb://..."}). Each name becomes a connectionId that the MongoDB tools can use directly, so one server can reach several deployments. Connections are opened on first use. Environment variable or config file only.
<MDB_MCP_DANGEROUS_HOST_BINDING>Environment variable OptionalWhen set to true, allows binding the HTTP server (and monitoring server) to a non-loopback host such as 0.0.0.0, a LAN IP, or an empty host (all interfaces). Binding to a non-loopback host exposes the server to the entire network and can allow unauthorized access. Off by default: the server refuses to start on a non-loopback host unless this is true.
<MDB_MCP_DISABLE_SERVER_SIDE_JS>Environment variable OptionalWhen set to true, disallows the use of server-side JavaScript operators (such as $where, $function, and $accumulator) in query filters and aggregation pipelines.
<MDB_MCP_DISABLE_UNTRUSTED_DATA_WARNING>Environment variable OptionalWhen set to true, tool responses include potentially untrusted data (such as documents or query results) as-is, without wrapping it in delimiters and a prompt-injection warning.
<MDB_MCP_DISABLED_TOOLS>Environment variable OptionalComma separated values of tool names, operation types, and/or categories of tools that will be disabled.
<MDB_MCP_DRY_RUN>Environment variable OptionalWhen true, runs the server in dry mode: dumps configuration and enabled tools, then exits without starting the server.
<MDB_MCP_ELICITATION_TIMEOUT_MS>Environment variable OptionalTime in milliseconds the user has to respond to an elicitation request (such as a tool confirmation prompt) before it fails.
<MDB_MCP_EVICTION_IDLE_GRACE_M_S>Environment variable OptionalHow long a session must be idle before it becomes eligible for least-recently-used eviction when the HTTP transport is at its maxSessions cap (only used when transport is 'http'). Swept back to idleTimeoutMs when larger.
<MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS>Environment variable OptionalTime in milliseconds between export cleanup cycles that remove expired export files.
<MDB_MCP_EXPORT_TIMEOUT_MS>Environment variable OptionalTime in milliseconds after which an export is considered expired and eligible for cleanup.
<MDB_MCP_EXPORTS_PATH>Environment variable OptionalFolder to store exported data files.
<MDB_MCP_EXTERNALLY_MANAGED_SESSIONS>Environment variable OptionalWhen true, the 2025-era HTTP transport accepts a session ID supplied externally through the 'mcp-session-id' header. When an external ID is supplied, the initialization request is optional, and an implicitly re-initialized session restores the client's previously negotiated capabilities from the session store.
<MDB_MCP_HEALTH_CHECK_HOST>Environment variable OptionalDeprecated. Use `monitoringServerHost` instead. Host address to bind the healthCheck HTTP server to (only used when transport is 'http'). If provided, `healthCheckPort` must also be set.
<MDB_MCP_HEALTH_CHECK_PORT>Environment variable OptionalDeprecated. Use `monitoringServerPort` instead. Port number for the healthCheck HTTP server (only used when transport is 'http'). If provided, `healthCheckHost` must also be set.
<MDB_MCP_HTTP_BODY_LIMIT>Environment variable OptionalMaximum size of the HTTP request body in bytes (only used when transport is 'http'). This value is passed as the optional limit parameter to the Express.js json() middleware.
<MDB_MCP_HTTP_HEADERS>Environment variable OptionalHeader that the HTTP server will validate when making requests (only used when transport is 'http').
<MDB_MCP_HTTP_HOST>Environment variable OptionalHost address to bind the HTTP server to (only used when transport is 'http').
<MDB_MCP_HTTP_PORT>Environment variable OptionalPort number for the HTTP server (only used when transport is 'http'). Use 0 for a random port.
<MDB_MCP_HTTP_RESPONSE_TYPE>Environment variable OptionalThe HTTP response type for tool responses: 'sse' for Server-Sent Events, 'json' for standard JSON responses.
<MDB_MCP_IDLE_TIMEOUT_MS>Environment variable OptionalIdle timeout for a client to disconnect (only applies to http transport).
<MDB_MCP_INDEX_CHECK>Environment variable OptionalWhen set to true, enforces that query operations must use an index, rejecting queries that perform a collection scan.
<MDB_MCP_LOG_PATH>Environment variable OptionalFolder to store logs.
<MDB_MCP_LOGGERS>Environment variable OptionalComma separated values of logger types.
<MDB_MCP_MAX_ACTIVE_CONNECTIONS>Environment variable OptionalMaximum number of MongoDB connections a single scope (an MCP session by default, see connectionScope) can hold open. When exceeded, the scope's least-recently-used connection is closed and its connectionId revoked. The preconfigured connection does not count towards the limit.
<MDB_MCP_MAX_BYTES_PER_QUERY>Environment variable OptionalThe maximum size in bytes for results from a find or aggregate tool call. This serves as an upper bound for the responseBytesLimit parameter in those tools.
<MDB_MCP_MAX_DOCUMENTS_PER_QUERY>Environment variable OptionalThe maximum number of documents that can be returned by a find or aggregate tool call. For the find tool, the effective limit will be the smaller of this value and the tool's limit parameter.
<MDB_MCP_MAX_SESSIONS>Environment variable OptionalMaximum number of concurrent sessions the HTTP transport will hold in memory (only used when transport is 'http'). Each session holds a full server instance, transport, and timers, so choose a value based on your deployment's available memory; the default is a conservative safety net rather than a recommended production value.
<MDB_MCP_MAX_TIME_M_S>Environment variable OptionalDeprecated. Use `timeoutMs` instead. The maximum time in milliseconds that operations are allowed to run on the MongoDB server.
<MDB_MCP_MCP_CLIENT_LOG_LEVEL>Environment variable OptionalMinimum severity level for log messages forwarded to the MCP client.
<MDB_MCP_MONITORING_SERVER_FEATURES>Environment variable OptionalFeatures to expose on the monitoring server: health-check, metrics, and process-metrics. process-metrics exposes /metrics with Node.js process metrics (only used when transport is 'http' and monitoringServerHost/monitoringServerPort are set).
<MDB_MCP_MONITORING_SERVER_HOST>Environment variable OptionalHost address to bind the monitoring HTTP server to (only used when transport is 'http'). If provided, `monitoringServerPort` must also be set.
<MDB_MCP_MONITORING_SERVER_PORT>Environment variable OptionalPort number for the monitoring HTTP server (only used when transport is 'http'). If provided, `monitoringServerHost` must also be set.
<MDB_MCP_NOTIFICATION_TIMEOUT_MS>Environment variable OptionalNotification timeout for a client to be aware of disconnect (only applies to http transport).
<MDB_MCP_PREVIEW_FEATURES>Environment variable OptionalComma separated values of preview features that are enabled.
<MDB_MCP_QUERY_COUNT_MAX_TIME_MS_CAP>Environment variable OptionalDeprecated. Use `queryCountTimeoutMs` instead.
<MDB_MCP_QUERY_COUNT_TIMEOUT_MS>Environment variable OptionalThe maximum time in milliseconds for the count phase of find operations. This is used to limit the time spent counting documents when determining if results were capped.
<MDB_MCP_READ_ONLY>Environment variable OptionalWhen set to true, only allows read, connect, and metadata operation types, disabling create/update/delete operations.
<MDB_MCP_TELEMETRY>Environment variable OptionalWhen set to disabled, disables telemetry collection.
<MDB_MCP_TIMEOUT_MS>Environment variable OptionalThe maximum time in milliseconds that MongoDB operations are allowed to run, applied as the driver's timeoutMS (client-side operation timeout, CSOT) on each connection. It bounds the entire operation, including server selection and network round trips.
<MDB_MCP_TRANSPORT>Environment variable OptionalEither 'stdio' or 'http'.
<MDB_MCP_VOYAGE_API_KEY>Environment variable Optional · SecretAPI key for Voyage AI embeddings service (required for creating Atlas Local deployments with auto-embed vector search capabilities).
Client compatibility
By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.
- Claude Code Transport supported
- Cursor Transport supported
- VS Code Client docs don’t list transports
- Codex Transport supported
- Devin Desktop Transport supported
- Gemini CLI Transport supported
- GitHub Copilot Client docs don’t list transports
- Cline Transport supported
- Kiro Transport supported
- Zed Client docs don’t list transports
- OpenCode Client docs don’t list transports
- JetBrains AI Assistant Transport supported
- Claude Client docs don’t list transports
- ChatGPT No shared transport
Sources
- Official MCP Registry registry.modelcontextprotocol.io · checked Nov 4, 2026
- MongoDB: vendor documentation mongodb.com · checked Nov 8, 2026
This data comes from the Official MCP Registry.