Skip to content

Commit 3bb127c

Browse files
chore: minor grammar mods
1 parent 1c46fda commit 3bb127c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -306,7 +306,7 @@ NOTE: atlas tools are only available when you set credentials on [configuration]
306306
- `collection-schema` - Describe the schema for a collection
307307
- `collection-storage-size` - Get the size of a collection in MB
308308
- `db-stats` - Return statistics about a MongoDB database
309-
- `export` - Export a query or aggregation results in the specified EJSON format.
309+
- `export` - Export query or aggregation results to EJSON format. Creates a uniquely named export accessible via the `exported-data` resource.
310310

311311
## 📄 Supported Resources
312312

@@ -339,9 +339,9 @@ The MongoDB MCP Server can be configured using multiple methods, with the follow
339339
| `httpHost` | `MDB_MCP_HTTP_HOST` | 127.0.0.1 | Host to bind the http server. |
340340
| `idleTimeoutMs` | `MDB_MCP_IDLE_TIMEOUT_MS` | 600000 | Idle timeout for a client to disconnect (only applies to http transport). |
341341
| `notificationTimeoutMs` | `MDB_MCP_NOTIFICATION_TIMEOUT_MS` | 540000 | Notification timeout for a client to be aware of diconnect (only applies to http transport). |
342-
| `exportsPath` | `MDB_MCP_EXPORTS_PATH` | see note\* | Folder to store the exported data to. |
343-
| `exportTimeoutMs` | `MDB_MCP_EXPORT_TIMEOUT_MS` | 300000 | Time in milliseconds, after which an export will be considered expired. |
344-
| `exportCleanupIntervalMs` | `MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS` | 120000 | Time in milliseconds which dictate how often a cleanup will be attempted for expired exports. |
342+
| `exportsPath` | `MDB_MCP_EXPORTS_PATH` | see note\* | Folder to store exported data files. |
343+
| `exportTimeoutMs` | `MDB_MCP_EXPORT_TIMEOUT_MS` | 300000 | Time in milliseconds after which an export is considered expired and eligible for cleanup. |
344+
| `exportCleanupIntervalMs` | `MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS` | 120000 | Time in milliseconds between export cleanup cycles that remove expired export files. |
345345

346346
#### Logger Options
347347

@@ -428,14 +428,14 @@ When index check mode is active, you'll see an error message if a query is rejec
428428

429429
#### Exports
430430

431-
The data exported by the `export` tool are temporarily stored in the configured `exportsPath` on the machine running the MCP server until cleaned up by the exports clean up cycle. If the `exportsPath` configuration is not provided then the following defaults are used:
431+
The data exported by the `export` tool is temporarily stored in the configured `exportsPath` on the machine running the MCP server until cleaned up by the export cleanup process. If the `exportsPath` configuration is not provided, the following defaults are used:
432432

433433
- **Windows:** `%LOCALAPPDATA%\mongodb\mongodb-mcp\exports`
434434
- **macOS/Linux:** `~/.mongodb/mongodb-mcp/exports`
435435

436-
The `exportTimeoutMs` configuration controls the time after which an export is considered to be expired. By default the value is 5 minutes and can be overridden using the config parameter.
436+
The `exportTimeoutMs` configuration controls the time after which the exported data is considered expired and eligible for cleanup. By default, exports expire after 5 minutes (300000ms).
437437

438-
The `exportCleanupIntervalMs` configuration controls how often the exports clean up cycle attempts to remove the expired exports. By default the value is 2 minutes and can be overridden using the config parameter.
438+
The `exportCleanupIntervalMs` configuration controls how frequently the cleanup process runs to remove expired export files. By default, cleanup runs every 2 minutes (120000ms).
439439

440440
#### Telemetry
441441

0 commit comments

Comments
 (0)