MongoDB Workspace

The MongoDB workspace is organized around databases, collections, documents, indexes, and GridFS instead of forcing documents into a relational model. It provides both a grid and full JSON view while preserving Extended JSON types such as ObjectId, dates, and long integers.

Connections and Drivers

Use a standard mongodb:// or mongodb+srv:// connection string and include replica set, authentication database, TLS, and other parameters in the URL when needed. Atlas, replica sets, and direct deployments share the same connection entry point.

DBX prefers the native MongoDB path. When a server or authentication protocol requires the older driver, you can select or automatically fall back to the mongodb-legacy Agent. The legacy path may expose fewer administration and mutation capabilities.

Databases and Collections

The object tree can:

List databases, collections, indexes, and GridFS buckets
Show document count, size, and other available collection statistics
Create, rename, or drop collections when using the writable native path
Drop databases, one index, or all deletable indexes except _id_
Open a document browser or query editor from a collection

Rename and destructive operations show the target and request preview and remain subject to read-only and production protection.

Document Browsing and Pagination

The document browser supports:

Paged reads with an estimated total
Grid and full-document views
Top-level and nested fields such as address.city
Searchable field selection, hidden columns, and persistent column layout
Quick filters plus multiple field conditions
Database-side sorting and collection queries

MongoDB totals may be estimated. In actively changing collections, the count and final page can shift while browsing.

Filters and Commands

Build field filters in the document browser or use shell-style commands in a MongoDB query tab. Completion can suggest collections, fields, query operators, update operators, aggregation stages, and cursor methods.

Examples:

db.users.find({ status: "active" }).sort({ createdAt: -1 })

db.orders.aggregate([
  { $match: { status: "paid" } },
  { $group: { _id: "$customerId", total: { $sum: "$amount" } } }
])

Use use <database> to switch the MongoDB query context.

Grid Editing

The grid expands common fields into columns and supports:

Editing top-level or nested fields
Adding and removing fields
Creating, cloning, and deleting documents
Copying selected documents as JSON, Markdown, or MongoDB Shell statements
Excluding _id when copying a new-document template
Reviewing pending update or delete targets before saving

Collections with very different document shapes are better handled in the full-document view so hidden fields are not overlooked.

JSON Document Editing

Document details can switch between a field tree and full JSON source:

Paste complete JSON when creating a document
Validate JSON syntax and root-object structure before save
Format, collapse, and copy nested objects or arrays
Preserve Extended JSON such as $oid, $date, and $numberLong
Change _id by creating the new document and removing the old one
Save full JSON with whole-document replacement semantics

Whole-document replacement writes the complete object back. Verify that the JSON contains every field that must be retained, especially in collections with concurrent updates.

Indexes

The object tree and collection structure can show index name, fields, uniqueness, and other metadata. When the native driver supports it, you can drop one index, drop all deletable indexes, or manage indexes through structure actions.

MongoDB preserves _id_, and sharding or other server rules may protect additional indexes. The server response is authoritative.

GridFS

The GridFS workspace manages buckets and files:

Browse, create, and delete buckets
Upload, download, preview, and delete files
Inspect filename, size, upload time, chunks, and metadata
Filter and sort files by fields
Export file lists or metadata

Dropping a bucket removes its files and chunks. Verify the bucket name and backup before doing this in production.

Copy and Export

Copy the current document, selected documents, or field values
Copy as plain JSON or Extended JSON that preserves type information
Use multi-format copy and export from the grid result
Exporting a MongoDB find result continues through the full result scope instead of only the currently displayed page, subject to query and export limits

Narrow filters before exporting a large collection and monitor server cursor use, network transfer, and local file size.

Safety and Compatibility Boundaries

Read-only connections block document, field, index, collection, database, and GridFS mutations
Production protection requires confirmation before recognizable writes
MCP Data read/write permits only scoped MongoDB mutations; opaque or effectively unbounded filters are high risk
The legacy Agent may not support native collection and index administration
Atlas permissions, authentication database, TLS, and IP allowlists are enforced by MongoDB
Paginated totals may be estimates and should not be treated as strongly consistent counts