Mongodb MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            ["/.dockerenv", "/run/.containerenv", "/var/run/.containerenv"].map(async (file) => {

            const exportFilePath = path.join(this.options.exportsDirectoryPath, exportNameWithExtension);

            execFileSync(binary, ["--version"], { timeout: 30_000, stdio: "ignore" });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mongodb-mcp-server -- npx -y mongodb-mcp-server

{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ]
    }
  }
}

[mcp_servers.mongodb-mcp-server]
command = "npx"
args = ["-y", "mongodb-mcp-server"]

{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ]
    }
  }
}

{
  "servers": {
    "mongodb-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: MDB_MCP_AGGREGATION_COUNT_MAX_TIME_MS_CAP (Deprecated. Use `aggregationCountTimeoutMs` instead), MDB_MCP_AGGREGATION_COUNT_TIMEOUT_MS (The 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 (When set to true, allows configuration values to be overridden via request headers and query parameters), MDB_MCP_API_CLIENT_ID (Atlas API client ID for authentication. Required for running Atlas tools), MDB_MCP_API_CLIENT_SECRET (Atlas API client secret for authentication. Required for running Atlas tools), MDB_MCP_ASSISTANT_BASE_URL (Base URL for the MongoDB Assistant API), MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS (Time 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 (Comma separated values of tool names that require user confirmation before execution. Requires the client to support elicitation), MDB_MCP_CONNECTION_IDLE_TIMEOUT_MS (Milliseconds 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 (Visibility 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 (MongoDB connection string for direct database connections. Optional, if not set, you'll need to call the connect tool before interacting with MongoDB data), MDB_MCP_DANGEROUS_HOST_BINDING (When 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 (When 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 (When 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 (Comma separated values of tool names, operation types, and/or categories of tools that will be disabled), MDB_MCP_DRY_RUN (When true, runs the server in dry mode: dumps configuration and enabled tools, then exits without starting the server), MDB_MCP_ELICITATION_TIMEOUT_MS (Time 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 (How 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 (Time in milliseconds between export cleanup cycles that remove expired export files), MDB_MCP_EXPORT_TIMEOUT_MS (Time in milliseconds after which an export is considered expired and eligible for cleanup), MDB_MCP_EXPORTS_PATH (Folder to store exported data files), MDB_MCP_EXTERNALLY_MANAGED_SESSIONS (When 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 (Deprecated. 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 (Deprecated. 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 (Maximum 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 (Header that the HTTP server will validate when making requests (only used when transport is 'http')), MDB_MCP_HTTP_HOST (Host address to bind the HTTP server to (only used when transport is 'http')), MDB_MCP_HTTP_PORT (Port number for the HTTP server (only used when transport is 'http'). Use 0 for a random port), MDB_MCP_HTTP_RESPONSE_TYPE (The HTTP response type for tool responses: 'sse' for Server-Sent Events, 'json' for standard JSON responses), MDB_MCP_IDLE_TIMEOUT_MS (Idle timeout for a client to disconnect (only applies to http transport)), MDB_MCP_INDEX_CHECK (When set to true, enforces that query operations must use an index, rejecting queries that perform a collection scan), MDB_MCP_LOG_PATH (Folder to store logs), MDB_MCP_LOGGERS (Comma separated values of logger types), MDB_MCP_MAX_ACTIVE_CONNECTIONS (Maximum 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 (The 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 (The 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 (Maximum 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 (Deprecated. Use `timeoutMs` instead. The maximum time in milliseconds that operations are allowed to run on the MongoDB server), MDB_MCP_MCP_CLIENT_LOG_LEVEL (Minimum severity level for log messages forwarded to the MCP client), MDB_MCP_MONITORING_SERVER_FEATURES (Features to expose on the monitoring server (only used when transport is 'http' and monitoringServerHost/monitoringServerPort are set)), MDB_MCP_MONITORING_SERVER_HOST (Host 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 (Port number for the monitoring HTTP server (only used when transport is 'http'). If provided, `monitoringServerHost` must also be set), MDB_MCP_NOTIFICATION_TIMEOUT_MS (Notification timeout for a client to be aware of disconnect (only applies to http transport)), MDB_MCP_PREVIEW_FEATURES (Comma separated values of preview features that are enabled), MDB_MCP_QUERY_COUNT_MAX_TIME_MS_CAP (Deprecated. Use `queryCountTimeoutMs` instead), MDB_MCP_QUERY_COUNT_TIMEOUT_MS (The 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 (When set to true, only allows read, connect, and metadata operation types, disabling create/update/delete operations), MDB_MCP_TELEMETRY (When set to disabled, disables telemetry collection), MDB_MCP_TIMEOUT_MS (The 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 (Either 'stdio' or 'http'), MDB_MCP_VOYAGE_API_KEY (API key for Voyage AI embeddings service (required for creating Atlas Local deployments with auto-embed vector search capabilities)).