Recern Workspace · Documentation

MongoDB

Workspace 0.3.0 adds MongoDB collections, documents, indexes, operations and a read-only JSON console. Compatibility checks cover MongoDB 8.0 standalone, password authentication, direct TLS and SSH without database TLS, including accounts with restricted permissions.

Connect

Choose MongoDB in New connection. Enter one host and port (27017 by default), username, password and the database to inspect. Authentication database is where the account was created; it defaults to admin and can differ from the database you browse. Passwords are stored in the system keychain.

This adapter uses a direct connection to one server. MongoDB connection strings, mongodb+srv, automatic replica discovery and Atlas-specific configurations are not supported or verified by this release.

For direct TLS, choose Required, verify certificate. An optional CA certificate file accepts a local PEM bundle, including a ~/ path. The supplied bundle becomes the trust source for that connection; server hostname verification remains enabled. Only the file path is saved. MongoDB TLS through SSH is not supported in 0.3.0. See SSH tunnels.

Views and permissions

  • Overview shows document and collection counts, storage, connections, resident memory, activity and findings. Monitoring requests contribute to the operation counters.
  • Collections lists up to 200 visible collections and their storage/index statistics. Views do not have independent storage statistics. At most four statistics requests run concurrently within an eight-second budget; unavailable or slow statistics leave the collection visible with an explanation.
  • Documents displays 50 documents per page. Choose a collection and enter a JSON filter object, such as {"status":"review"}. Narrow large results with a filter before paging.
  • Indexes shows the selected collection's index definitions.
  • Operations displays up to 100 current operations when permissions allow it. The view identifies whether it can see all operations or only the account's own operations.
  • Console accepts the read-only JSON commands below and includes history, saved queries, cancellation and JSON export.

Use a database account with read access to the target database. Additional monitoring permissions, such as clusterMonitor, make server diagnostics available. Missing monitoring permissions are reported without blocking authorized document reads; Workspace never grants permissions or changes server settings.

Read-only JSON console

Enter one JSON command object, not a mongosh script. For example, against the local fintech demo:

{"find":"merchants","filter":{"status":"review"},"sort":{"risk_score":-1},"limit":50}
{"count":"merchants","query":{"status":"review"}}

Supported commands are find, aggregate, count and explain for a find command. Common filtering, projection, sorting and grouping stages are supported. Nested lookup/facet/union pipelines, writes, administrative commands and server-side JavaScript are refused. The console remains read-only even if a saved connection is manually edited to disable Safe Mode.

The default limit is 100 documents, with a maximum of 1,000 and an 8 MiB response budget. Commands have a ten-second server limit and a fifteen-second client deadline. Cancel stops the client wait and drops its cursor; server work remains subject to maxTimeMS.

Export

JSON exports only the displayed documents as Extended JSON, preserving BSON types such as ObjectId, dates and large integers. It is not a complete collection dump. See query history, saved queries and export.