MongoDB Compass
A graphical MongoDB client for local deployments, replica sets, sharded clusters and Atlas, with document and schema browsing, queries, aggregations, index analysis, import, export and explain plans.
What MongoDB Compass provides
Compass helps inspect BSON documents and schema distributions, build filters and aggregation pipelines, view Explain plans, manage indexes and perform controlled import or export. It lowers the barrier to MongoDB operations but does not replace server roles, backups, change review or performance monitoring.
Read-only and connection boundaries
A client read-only switch reduces accidental edits, while the real boundary is the database role. Use a server account with only database-level read permission for review tasks, trusted TLS and a controlled network. Connection strings, certificates, OIDC sessions and exported documents should be handled as credentials or business data.
Maintenance note
This page reviews MongoDB Compass 1.49.9, platform packages, TLS and authentication, read-only mode, telemetry, query and index analysis, and SSPL-1.0 licensing. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave MongoDB Compass to this cloud drive
Baidu Netdisk
Save MongoDB Compass to this cloud drive
MongoDB Compass 1.49.9 read-only connection and query analysis guide
Connect to a test database with a dedicated read-only account, verify TLS and a small query, then analyze Explain output before considering index or data changes.
Before you start
- Prepare a connection string, database name and least-privilege account; Atlas also needs a controlled network allowlist.
- For private deployments, prepare a trusted CA and confirm replica-set name, authentication database and DNS or SRV resolution.
- Complete a snapshot or native backup before production access and define query timeout, read preference and allowed operations.
Installation steps
- 01
Install the 1.49.9 package
Choose Windows x64, the macOS Intel or Apple silicon build, or the matching Linux package, and verify version and architecture.
- 02
Review privacy and read-only settings
Inspect usage-statistics settings and enable readOnly for a review workstation, while still enforcing a read-only database role on the server.
- 03
Protect connection information
Use explicit TLS or an SRV connection with a verified certificate and hostname, and keep plaintext passwords out of history, tickets and screenshots.
Quick start
- 01
Verify target and role
After connecting, check host, cluster, database and current user, open only a test collection and confirm that write or administration operations are rejected.
- 02
Build a filter and pipeline
Validate BSON types, time zones and missing fields with a small result set, build the pipeline in stages and remove customer identifiers or tokens before saving.
- 03
Inspect Explain and indexes
Review scanned documents, returned documents and index use; test index changes with staging data and record space, build-time and write-impact observations.
Usage tips
- BSON types such as ObjectId, Decimal128, dates and arrays need explicit handling during import and export.
- Aggregation stages such as $out or $merge write data; inspect every stage before running a pasted pipeline.
- Telemetry, connection strings and exports can contain topology, queries or business data; redact them in diagnostics.
Troubleshooting and uninstall
Why does an SRV connection fail?
Check DNS SRV and TXT records, proxy, network allowlist, system time and connection-string encoding, then test the same account with a controlled client.
Why can the client connect but not show a database?
Check authentication database, roles and whether a visible collection exists. Do not elevate to an administrator role just to make an empty database appear.
- Export safe templates and revoke sessionsSave redacted queries and pipelines, disconnect, and revoke unused Atlas, OIDC or certificate sessions.
- Clear local sensitive dataUninstall Compass, remove saved connections, caches, logs and temporary exports, and rotate passwords that appeared in history or connection strings.
Frequently asked questions
Does MongoDB Compass include a MongoDB server?
No. It is a client that connects to an existing local deployment, remote cluster or Atlas service.
Does the Compass read-only switch guarantee read-only access?
The server role is the real boundary. Use a database account with only read permission and treat the client switch as an additional guard against accidental edits.
What telemetry does Compass collect?
The standard build may collect anonymous aggregate usage and error data. Review the privacy setting and configuration for the deployment, and disable it when the environment requires isolation.