The MCP Server has various options that you can set to connect to a MongoDB cluster and control MCP Server operations. You can set the options in a JSON configuration file, through a command line, or using operating system environment variables.
Options List
Use the following configuration options to configure the MCP Server.
Important
If you're a MongoDB Enterprise or MongoDB Atlas user and you require a specific authentication mechanism, see the MongoDB MCP Server Security section to learn about the configuration options for your authentication method.
CLI Option Name | OS Environment Variable Name | Type | Default | Description |
|---|---|---|---|---|
|
| string | Not set | Atlas API client ID for authentication. |
|
| string | Not set | Atlas API client secret for authentication. |
|
| string | Not set | Connection string for a direct database connection. Sets the connection string at runtime to allow the client to directly connect to a cluster. ImportantThe NoteTypically, avoid providing the connection string at runtime because you expose the connection credentials to the large language model. The connection string is used if the client has never connected before, or the client switches the connection to a new cluster if the client was previously connected. After the client calls the connect or switch connection tool, the client reuses the same connection for subsequent operations. Therefore, you only need to call the connect or switch connection tool once or if you need to switch to a different connection. |
|
| boolean |
| Use the dry-run option to examine your MCP Server configuration. When you enable the dry-run option, the MCP Server returns the MCP Server configuration settings and the list of enabled MongoDB MCP Server Tools. To enable the dry-run option, set For more information, see Enabling MCP Server Dry-Run Mode. |
|
| string |
| Specifies where the MCP Server sends the logs. Set
For example, to set To set the For more information about the logging options, see Troubleshoot MongoDB MCP Server. |
|
| string | Depends on the operating system | Directory that stores the MCP Server logs. For more information about the log path and operating system specifics, see Troubleshoot MongoDB MCP Server. |
|
| array | Not set | An array of MCP tool names, operation types, or tool categories to disable. For more information, see Disabling MCP Server Tools. |
|
| boolean |
| To disable cluster write operations, set Default is to allow cluster write operations. Typically, always enable read-only mode. For more information, see Enabling MCP Server Read-Only Mode. |
|
| boolean |
| If For more information, see Enabling Index Check. |
|
| string |
| If For more information, see Disabling MCP Server Telemetry. |
|
| string |
| Transport protocol for communications with the MCP Server. Set
|
|
| integer |
| IP port number for HTTP communications with the MCP Server. |
|
| string |
| IP address for HTTP communications with the MCP Server. With Streamable HTTP, the MCP Server is bound to WarningBinding to To learn more, see Remote Connections. |
|
| integer |
| Idle timeout for a client to disconnect. Only applies to HTTP transport. |
|
| integer |
| Notification timeout for a client to be aware of disconnect. Only applies to HTTP transport. |
|
| string |
| SCRAM is the default authentication mechanism for MongoDB. To connect to your MongoDB deployments with the MongoDB MCP server using other authentication methods, see the following pages: |
|
| string | Depends on the operating system | Directory that stores exported data files. For more information about the export path and operating system specifics, see Export Data from MongoDB MCP Server. |
|
| integer |
| Time in milliseconds after which exported data files are eligible for deletion by the MCP Server cleanup process. |
|
| integer |
| Time period in milliseconds between automatic executions of the MCP Server cleanup process that deletes expired export data files. The cleanup process is run automatically. |
|
| string | Not set | Comma separated values of preview features that are enabled.
Valid values: |
Vector Search Options
Vector search support in MCP is available as a preview feature.
To enable this feature, set the previewFeatures flag or
MDB_MCP_PREVIEW_FEATURES environment variable to
search in your MCP configuration.
To learn more, see MongoDB MCP Server Configuration Options.
The following options configure the MCP server's behavior when you use it to work with MongoDB Vector Search.
CLI Option Name | OS Environment Variable Name | Type | Default | Description |
|---|---|---|---|---|
|
| string | Not set | Voyage AI API key for automatic embedding generation. When you configure this option, the MCP Server automatically generates embeddings for:
The MCP Server also validates that fields with vector search indexes contain valid embedding vectors to prevent breaking vector search indexes. The MongoDB MCP server supports the following Voyage AI models:
To learn more about Voyage AI, see the Voyage AI documentation. For additional vector search configuration options, see Vector Search Options. |
|
| boolean |
| When set to By default, the MCP Server validates that fields with vector search indexes contain valid embedding vectors with the correct dimensions to prevent breaking vector search indexes. Enable this option to allow inserting raw values into embeddings fields without validation. WarningDisabling embeddings validation may result in documents with invalid embeddings that cannot be used with vector search indexes. |
|
| integer |
| Default number of dimensions for vector search embeddings. This value is used when creating vector search indexes and validating embeddings. |
|
| string |
| Default similarity function for vector search. Set to one of the following values:
The MCP server uses this value is as the default when creating vector search indexes unless specified otherwise. To learn more, see How to Index Fields for Vector Search. |
Positional Arguments
The MCP Server accepts a positional argument that can be provided without specifying a CLI flag. The first positional argument is interpreted as the connection string for your MongoDB deployment.
As a security best practice, use the MDB_MCP_CONNECTION_STRING
environment variable to set the connection string. If environment variables
are not an option, use the first positional argument. For example:
"args": [ "-y", "mongodb-mcp-server", "mongodb+srv://<user-name>:<password>@<cluster-name>.mongodb.net/", "--readOnly" ]