Understand MongoDB documents without losing the bigger picture.

Explore databases, collections, views, indexes, and sampled document shapes; work safely with records; and connect MongoDB to the transformations, lineage, and tools around it.

Type
Document database
Explore
Database → collection, view, or index
Connect with
Hostname or MongoDB SRV URL, database, credentials, port, and supported TLS options

What WhoDB lets your team do with MongoDB

Move from exploring MongoDB to building useful workflows, shared tools, and trusted data products—all without losing the context behind the work.

Updated August 25, 2026. Available actions depend on the permissions granted to your connected account.

Browse MongoDB on its own terms

Move through databases and collections, inspect documents in grid or JSON views, and keep indexes and read-only views visible in a workflow designed for document data.

Make flexible documents easier to reason about

WhoDB samples collection data to show useful fields and data types while clearly labeling the result as a sample rather than a fixed schema.

Handle document operations directly

Create collections, add documents, update or delete records, and generate representative mock documents while respecting the connected user's permissions.

Connect documents to wider data workflows

Use MongoDB data inside project transformations, lineage, semantic models, functions, and apps alongside the SQL, analytical, cloud, and business systems it interacts with.

From connected data to a workflow people can trust

Connect directly or with SRV

Use a normal host or a MongoDB SRV connection URL, with supported authentication and TLS options for the environment.

Inspect real document shapes

Browse collections and documents, review sampled fields and types, and inspect indexes before making assumptions about flexible data.

Bring MongoDB into a shared workflow

Combine document data with other project sources through visible transformations and keep execution history beside the logic.

Trace what depends on the result

Follow project relationships into datasets, transforms, models, functions, and apps so a collection change is not evaluated in isolation.

A MongoDB GUI for cross-source work

MongoDB's flexible model is valuable precisely because it is not a table with a rigid schema. WhoDB preserves that distinction through document-oriented browsing and sampled metadata, then gives the team a shared place to connect those documents to everything downstream.

WhoDB gives MongoDB teams a clear way to browse collections, understand document structure, edit data, generate mock documents, and see relationships across the wider project.

WhoDB is a strong fit for

  • Teams investigating changing or inconsistent document shapes
  • Operations workflows that combine MongoDB with relational data
  • Engineers who need document editing plus downstream context
  • Organizations replacing collection exports and manual handoffs

MongoDB integration questions

Straight answers about setup, everyday tasks, and how WhoDB fits into your workflow.

Does WhoDB support MongoDB SRV connection URLs?

Yes. The MongoDB connection flow accepts a hostname or MongoDB SRV URL, plus database, authentication, port, and supported TLS settings.

How does WhoDB show a MongoDB schema?

WhoDB samples documents to show useful fields and data types. Because documents in one MongoDB collection can have different shapes, WhoDB clearly labels this as a sample rather than a fixed schema.

Can WhoDB edit MongoDB documents?

Yes. Teams can create collections, insert and update documents, delete data, and generate mock documents when their MongoDB permissions allow it.

Does WhoDB replace MongoDB Compass completely?

WhoDB is the stronger fit when MongoDB work must continue into cross-source transformations, lineage, semantic models, apps, or functions. Teams needing specialist MongoDB administration or a full Mongo shell may still use a dedicated tool alongside it.