You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -360,6 +360,7 @@ The MongoDB MCP Server can be configured using multiple methods, with the follow
360
360
|`exportTimeoutMs`|`MDB_MCP_EXPORT_TIMEOUT_MS`| 300000 | Time in milliseconds after which an export is considered expired and eligible for cleanup. |
361
361
|`exportCleanupIntervalMs`|`MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS`| 120000 | Time in milliseconds between export cleanup cycles that remove expired export files. |
362
362
|`atlasTemporaryDatabaseUserLifetimeMs`|`MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS`| 14400000 | Time in milliseconds that temporary database users created when connecting to MongoDB Atlas clusters will remain active before being automatically deleted. |
363
+
|`voyageApiKey`|`MDB_VOYAGE_API_KEY`| <notset> | API key for communicating with Voyage AI. Used for generating embeddings for Vector search. |
0 commit comments