MongoDB & Atlas
Connect local MongoDB and MongoDB Atlas correctly — the platform distinguishes them automatically.
Local vs Atlas — handled for you
The platform detects how a MongoDB host should connect and applies the right scheme and TLS, so you don’t have to.
- Atlas cluster host (e.g. cluster0.xxxxx.mongodb.net): connects over mongodb+srv with TLS — no port needed.
- Atlas shard-member host (…-shard-00-0N…mongodb.net): connects directly over TLS (these have no SRV record).
- Local / self-hosted (host:port): connects with your chosen SSL mode.
- Backups and restores (mongodump / mongorestore) use the exact same rules — no drift between connecting and backing up.
IP allow-listing (per connection)
Atlas only accepts connections from allow-listed IPs. Under Governance → Network Access, pick a MongoDB connection and connect its Atlas project once with an Atlas API key (stored encrypted, verified against Atlas). From then on you can view the project’s current access list, add or remove rules, and quick-add the platform’s public egress IP — all from the tool, per connection, fully audited.
Querying MongoDB
MongoDB isn’t SQL, so the Query Console gives it a dedicated runner — see the Query console & runners guide.
Try it yourself
Open the console and put this into practice.