Skip to content
MCP server

Mongodb MCP Server

Open-source MCP server letting AI assistants query and manage MongoDB and Atlas clusters

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, API, self-hosted
Runs
Locally
Version
3.3.0
Listing updated
today

Similar MCP servers

About Mongodb MCP Server

Mongodb MCP Server is an open-source MCP server for databases. It runs locally on your machine and is started by your AI client.

The README describes this as a Model Context Protocol server that gives AI clients access to MongoDB databases and MongoDB Atlas. It runs locally over stdio and is distributed as an npm package, with Docker images and one-click install links for several editors. Read-only mode is recommended in the setup examples, and write operations can be enabled by removing that flag.

The server exposes database tools for querying, aggregation, indexes, schema inspection, and data changes, plus a separate set of Atlas tools for managing projects, clusters, users, and access lists when Atlas API credentials are configured. Destructive operations such as dropping collections or deleting many documents can be set to require user confirmation. Connections can be a single connection string or several named ones.

It suits developers and data teams who want an assistant to explore or administer MongoDB deployments from an editor or agent client. The README also points to a separate hosted Atlas-managed MCP server as the recommended route for Atlas users.

Install

Run in a terminal

claude mcp add mongodb-mcp-server --env MDB_MCP_API_CLIENT_ID='<MDB_MCP_API_CLIENT_ID>' --env MDB_MCP_API_CLIENT_SECRET='<MDB_MCP_API_CLIENT_SECRET>' --env MDB_MCP_CONNECTION_STRING='<MDB_MCP_CONNECTION_STRING>' --env MDB_MCP_CONNECTION_STRINGS='<MDB_MCP_CONNECTION_STRINGS>' --env MDB_MCP_VOYAGE_API_KEY='<MDB_MCP_VOYAGE_API_KEY>' -- npx -y mongodb-mcp-server

Add to claude_desktop_config.json

{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ],
      "env": {
        "MDB_MCP_API_CLIENT_ID": "<MDB_MCP_API_CLIENT_ID>",
        "MDB_MCP_API_CLIENT_SECRET": "<MDB_MCP_API_CLIENT_SECRET>",
        "MDB_MCP_CONNECTION_STRING": "<MDB_MCP_CONNECTION_STRING>",
        "MDB_MCP_CONNECTION_STRINGS": "<MDB_MCP_CONNECTION_STRINGS>",
        "MDB_MCP_VOYAGE_API_KEY": "<MDB_MCP_VOYAGE_API_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ],
      "env": {
        "MDB_MCP_API_CLIENT_ID": "<MDB_MCP_API_CLIENT_ID>",
        "MDB_MCP_API_CLIENT_SECRET": "<MDB_MCP_API_CLIENT_SECRET>",
        "MDB_MCP_CONNECTION_STRING": "<MDB_MCP_CONNECTION_STRING>",
        "MDB_MCP_CONNECTION_STRINGS": "<MDB_MCP_CONNECTION_STRINGS>",
        "MDB_MCP_VOYAGE_API_KEY": "<MDB_MCP_VOYAGE_API_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "mongodb-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ],
      "env": {
        "MDB_MCP_API_CLIENT_ID": "<MDB_MCP_API_CLIENT_ID>",
        "MDB_MCP_API_CLIENT_SECRET": "<MDB_MCP_API_CLIENT_SECRET>",
        "MDB_MCP_CONNECTION_STRING": "<MDB_MCP_CONNECTION_STRING>",
        "MDB_MCP_CONNECTION_STRINGS": "<MDB_MCP_CONNECTION_STRINGS>",
        "MDB_MCP_VOYAGE_API_KEY": "<MDB_MCP_VOYAGE_API_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ],
      "env": {
        "MDB_MCP_API_CLIENT_ID": "<MDB_MCP_API_CLIENT_ID>",
        "MDB_MCP_API_CLIENT_SECRET": "<MDB_MCP_API_CLIENT_SECRET>",
        "MDB_MCP_CONNECTION_STRING": "<MDB_MCP_CONNECTION_STRING>",
        "MDB_MCP_CONNECTION_STRINGS": "<MDB_MCP_CONNECTION_STRINGS>",
        "MDB_MCP_VOYAGE_API_KEY": "<MDB_MCP_VOYAGE_API_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server"
      ],
      "env": {
        "MDB_MCP_API_CLIENT_ID": "<MDB_MCP_API_CLIENT_ID>",
        "MDB_MCP_API_CLIENT_SECRET": "<MDB_MCP_API_CLIENT_SECRET>",
        "MDB_MCP_CONNECTION_STRING": "<MDB_MCP_CONNECTION_STRING>",
        "MDB_MCP_CONNECTION_STRINGS": "<MDB_MCP_CONNECTION_STRINGS>",
        "MDB_MCP_VOYAGE_API_KEY": "<MDB_MCP_VOYAGE_API_KEY>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • MDB_MCP_AGGREGATION_COUNT_MAX_TIME_MS_CAPDeprecated. Use `aggregationCountTimeoutMs` instead.
  • MDB_MCP_AGGREGATION_COUNT_TIMEOUT_MSThe 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_OVERRIDESWhen set to true, allows configuration values to be overridden via request headers and query parameters.
  • MDB_MCP_API_CLIENT_IDAtlas API client ID for authentication. Required for running Atlas tools.
  • MDB_MCP_API_CLIENT_SECRETAtlas API client secret for authentication. Required for running Atlas tools.
  • MDB_MCP_ASSISTANT_BASE_URLBase URL for the MongoDB Assistant API.
  • MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MSTime in milliseconds that temporary database users created when connecting to MongoDB Atlas clusters will remain active before being automatically deleted.
  • MDB_MCP_CONFIRMATION_REQUIRED_TOOLSComma separated values of tool names that require user confirmation before execution. Requires the client to support elicitation.
  • MDB_MCP_CONNECTION_IDLE_TIMEOUT_MSMilliseconds 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_SCOPEVisibility 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_STRINGMongoDB 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_STRINGSMongoDB 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_BINDINGWhen 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_JSWhen 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_WARNINGWhen 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_TOOLSComma separated values of tool names, operation types, and/or categories of tools that will be disabled.
  • MDB_MCP_DRY_RUNWhen true, runs the server in dry mode: dumps configuration and enabled tools, then exits without starting the server.
  • MDB_MCP_ELICITATION_TIMEOUT_MSTime 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_SHow 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_MSTime in milliseconds between export cleanup cycles that remove expired export files.
  • MDB_MCP_EXPORT_TIMEOUT_MSTime in milliseconds after which an export is considered expired and eligible for cleanup.
  • MDB_MCP_EXPORTS_PATHFolder to store exported data files.
  • MDB_MCP_EXTERNALLY_MANAGED_SESSIONSWhen 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_HOSTDeprecated. 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_PORTDeprecated. 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_LIMITMaximum 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_HEADERSHeader that the HTTP server will validate when making requests (only used when transport is 'http').
  • MDB_MCP_HTTP_HOSTHost address to bind the HTTP server to (only used when transport is 'http').
  • MDB_MCP_HTTP_PORTPort number for the HTTP server (only used when transport is 'http'). Use 0 for a random port.
  • MDB_MCP_HTTP_RESPONSE_TYPEThe HTTP response type for tool responses: 'sse' for Server-Sent Events, 'json' for standard JSON responses.
  • MDB_MCP_IDLE_TIMEOUT_MSIdle timeout for a client to disconnect (only applies to http transport).
  • MDB_MCP_INDEX_CHECKWhen set to true, enforces that query operations must use an index, rejecting queries that perform a collection scan.
  • MDB_MCP_LOG_PATHFolder to store logs.
  • MDB_MCP_LOGGERSComma separated values of logger types.
  • MDB_MCP_MAX_ACTIVE_CONNECTIONSMaximum 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_QUERYThe 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_QUERYThe 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_SESSIONSMaximum 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_SDeprecated. Use `timeoutMs` instead. The maximum time in milliseconds that operations are allowed to run on the MongoDB server.
  • MDB_MCP_MCP_CLIENT_LOG_LEVELMinimum severity level for log messages forwarded to the MCP client.
  • MDB_MCP_MONITORING_SERVER_FEATURESFeatures 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_HOSTHost 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_PORTPort number for the monitoring HTTP server (only used when transport is 'http'). If provided, `monitoringServerHost` must also be set.
  • MDB_MCP_NOTIFICATION_TIMEOUT_MSNotification timeout for a client to be aware of disconnect (only applies to http transport).
  • MDB_MCP_PREVIEW_FEATURESComma separated values of preview features that are enabled.
  • MDB_MCP_QUERY_COUNT_MAX_TIME_MS_CAPDeprecated. Use `queryCountTimeoutMs` instead.
  • MDB_MCP_QUERY_COUNT_TIMEOUT_MSThe 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_ONLYWhen set to true, only allows read, connect, and metadata operation types, disabling create/update/delete operations.
  • MDB_MCP_TELEMETRYWhen set to disabled, disables telemetry collection.
  • MDB_MCP_TIMEOUT_MSThe 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_TRANSPORTEither 'stdio' or 'http'.
  • MDB_MCP_VOYAGE_API_KEYAPI key for Voyage AI embeddings service (required for creating Atlas Local deployments with auto-embed vector search capabilities).
  • MDB_MCP_AGGREGATION_COUNT_MAX_TIME_MS_CAPDeprecated. Use `aggregationCountTimeoutMs` instead.
  • MDB_MCP_AGGREGATION_COUNT_TIMEOUT_MSThe 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_OVERRIDESWhen set to true, allows configuration values to be overridden via request headers and query parameters.
  • MDB_MCP_API_CLIENT_IDAtlas API client ID for authentication. Required for running Atlas tools.
  • MDB_MCP_API_CLIENT_SECRETAtlas API client secret for authentication. Required for running Atlas tools.
  • MDB_MCP_ASSISTANT_BASE_URLBase URL for the MongoDB Assistant API.
  • MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MSTime in milliseconds that temporary database users created when connecting to MongoDB Atlas clusters will remain active before being automatically deleted.
  • MDB_MCP_CONFIRMATION_REQUIRED_TOOLSComma separated values of tool names that require user confirmation before execution. Requires the client to support elicitation.
  • MDB_MCP_CONNECTION_IDLE_TIMEOUT_MSMilliseconds 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_SCOPEVisibility 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_STRINGMongoDB 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_STRINGSMongoDB 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_BINDINGWhen 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_JSWhen 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_WARNINGWhen 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_TOOLSComma separated values of tool names, operation types, and/or categories of tools that will be disabled.
  • MDB_MCP_DRY_RUNWhen true, runs the server in dry mode: dumps configuration and enabled tools, then exits without starting the server.
  • MDB_MCP_ELICITATION_TIMEOUT_MSTime 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_SHow 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_MSTime in milliseconds between export cleanup cycles that remove expired export files.
  • MDB_MCP_EXPORT_TIMEOUT_MSTime in milliseconds after which an export is considered expired and eligible for cleanup.
  • MDB_MCP_EXPORTS_PATHFolder to store exported data files.
  • MDB_MCP_EXTERNALLY_MANAGED_SESSIONSWhen 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_HOSTDeprecated. 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_PORTDeprecated. 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_LIMITMaximum 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_HEADERSHeader that the HTTP server will validate when making requests (only used when transport is 'http').
  • MDB_MCP_HTTP_HOSTHost address to bind the HTTP server to (only used when transport is 'http').
  • MDB_MCP_HTTP_PORTPort number for the HTTP server (only used when transport is 'http'). Use 0 for a random port.
  • MDB_MCP_HTTP_RESPONSE_TYPEThe HTTP response type for tool responses: 'sse' for Server-Sent Events, 'json' for standard JSON responses.
  • MDB_MCP_IDLE_TIMEOUT_MSIdle timeout for a client to disconnect (only applies to http transport).
  • MDB_MCP_INDEX_CHECKWhen set to true, enforces that query operations must use an index, rejecting queries that perform a collection scan.
  • MDB_MCP_LOG_PATHFolder to store logs.
  • MDB_MCP_LOGGERSComma separated values of logger types.
  • MDB_MCP_MAX_ACTIVE_CONNECTIONSMaximum 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_QUERYThe 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_QUERYThe 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_SESSIONSMaximum 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_SDeprecated. Use `timeoutMs` instead. The maximum time in milliseconds that operations are allowed to run on the MongoDB server.
  • MDB_MCP_MCP_CLIENT_LOG_LEVELMinimum severity level for log messages forwarded to the MCP client.
  • MDB_MCP_MONITORING_SERVER_FEATURESFeatures 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_HOSTHost 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_PORTPort number for the monitoring HTTP server (only used when transport is 'http'). If provided, `monitoringServerHost` must also be set.
  • MDB_MCP_NOTIFICATION_TIMEOUT_MSNotification timeout for a client to be aware of disconnect (only applies to http transport).
  • MDB_MCP_PREVIEW_FEATURESComma separated values of preview features that are enabled.
  • MDB_MCP_QUERY_COUNT_MAX_TIME_MS_CAPDeprecated. Use `queryCountTimeoutMs` instead.
  • MDB_MCP_QUERY_COUNT_TIMEOUT_MSThe 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_ONLYWhen set to true, only allows read, connect, and metadata operation types, disabling create/update/delete operations.
  • MDB_MCP_TELEMETRYWhen set to disabled, disables telemetry collection.
  • MDB_MCP_TIMEOUT_MSThe 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_TRANSPORTEither 'stdio' or 'http'.
  • MDB_MCP_VOYAGE_API_KEYAPI key for Voyage AI embeddings service (required for creating Atlas Local deployments with auto-embed vector search capabilities).

Tools this server provides (9)

Taken from the project documentation; the running server may differ.

aggregate
Run an aggregation against a MongoDB collection
find
Run a find query against a MongoDB collection
count
Gets the number of documents in a MongoDB collection
collection-schema
Describe the schema for a collection
collection-indexes
Describe the indexes for a collection
create-index
Create an index for a collection
delete-many
Removes all documents that match the filter from a MongoDB collection
atlas-list-clusters
List MongoDB Atlas clusters
atlas-create-free-cluster
Create a free MongoDB Atlas cluster

What it does

Database query tools
Run find, aggregate, count, and export operations against collections from an MCP client.
Schema and index inspection
Describe collection schemas, list indexes, and create or drop indexes.
Atlas management tools
Create and inspect Atlas projects, clusters, database users, and IP access lists with service account credentials.
Read-only mode
A --readOnly flag limits the server to non-mutating access, which the setup examples enable by default.
Confirmation for destructive tools
Selected tools such as drop-database and delete-many can require user approval before running.
Multiple named connections
Connection strings can be keyed by name so one server reaches several deployments.

Good for

  • Asking an AI assistant to explore collections and sample documents during development
  • Checking index usage and performance advisor suggestions for slow queries
  • Provisioning a test Atlas cluster or sample dataset from an editor
  • Letting an agent run aggregations against analytics data in read-only mode

Pricing

Open source

Open-source server run locally or via Docker; Atlas itself is billed separately by MongoDB.

Mongodb MCP Server FAQ

Does it need a running MongoDB instance?

It connects to a MongoDB connection string for self-managed or Atlas deployments, or to Atlas through API credentials. The README says the connection string can point to a local instance or an Atlas cluster.

Can it run without write access?

Yes. The setup examples include --readOnly, and the README says to remove that flag only if write operations are needed.

What is required to use the Atlas tools?

Atlas tools need Atlas Service Account API credentials, with client ID and secret set as environment variables.

What Node version is required?

The README says at least Node.js v22.13.0 and notes that Node 20 support is deprecated.

Is Mongodb MCP Server free?

Yes. Mongodb MCP Server is open source, so you can use and self-host it for free.

How do I add Mongodb MCP Server to Claude Code?

Run this command in your terminal: claude mcp add mongodb-mcp-server --env MDB_MCP_API_CLIENT_ID='<MDB_MCP_API_CLIENT_ID>' --env MDB_MCP_API_CLIENT_SECRET='<MDB_MCP_API_CLIENT_SECRET>' --env MDB_MCP_CONNECTION_STRING='<MDB_MCP_CONNECTION_STRING>' --env MDB_MCP_CONNECTION_STRINGS='<MDB_MCP_CONNECTION_STRINGS>' --env MDB_MCP_VOYAGE_API_KEY='<MDB_MCP_VOYAGE_API_KEY>' -- npx -y mongodb-mcp-server

What are the best alternatives to Mongodb MCP Server?

The closest alternatives to Mongodb MCP Server are MCP Toolbox for Databases, Db Conn MCP, Mysql, MCP Server Couchbase and Metabase MCP (headless).

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers