mongodb

MongoDB

Name: Nexoxa Bridge
Author: Nexoxa

Document databases via mongodb:// and mongodb+srv:// — collections, indexes, and JSON editing.

DOCmongodb://user:password@host:27017/admin

The story

These pages use illustrative scenarios (sample names and timelines) to explain real Nexoxa Bridge features. Connection URLs, sidebar panels, and vault behavior match the product; story details are teaching examples, not customer case studies.

Alex manages three MongoDB surfaces: Atlas production with mongodb+srv://, a staging replica set on plain mongodb://, and a laptop docker instance with no auth for local feature work. Connection strings used to live in 1Password entries copied into Compass one at a time.

Alex pasted each URL into Bridge — Atlas Prod, Staging RS, Local Dev — and watched collections appear like a schema tree. Auth database and SRV records parsed automatically; passwords never appeared in Copilot prompts. A document with a bad nested field was fixed in the JSON editor while a Postgres migration ran in the next tab.

Document databases deserve document-native browsing, not SQL metaphors forced sideways.

Connection URL

Scheme: mongodb://

Parameters

MongoDB (with auth)stringvaultrequired

mongodb://user:password@host:27017/admin

MongoDB (no auth)stringvaultrequired

mongodb://host:27017/mydb

MongoDB Atlas (SRV)stringvaultrequired

mongodb+srv://user:[email protected]/mydb

Paste the URL in Nexoxa Bridge → New connection. Save a human-readable name — MCP references that name, not the raw URL with embedded passwords.

Step 1

Collections & indexes

Alex expands the orders database and sees collections beside their indexes — including the compound index on customer_id and created_at that explains slow dashboards. No db.orders.getIndexes() typing.
Atlas SRV URLs resolve on connect; local dev works without user/password in the URL.

Supports mongodb:// and mongodb+srv://. Auth database path segment (e.g. /admin) honored. Collections listed with index metadata. Multiple saved connections for Atlas, self-hosted, and local instances.

Step 2

JSON documents

A bug report shows malformed metadata on one order document. Alex finds the _id in the grid, opens the structured JSON editor, fixes the nested object, and saves — BSON types respected in the UI.
Query helpers filter by field without writing a full aggregation pipeline for simple lookups.

Document editor for BSON-backed fields with validation feedback. Collection browsing and query execution in the same workspace. mongodb+srv:// for Atlas cluster discovery.

Step 3

MongoDB shell

For heavier work Alex switches to the MongoDB shell tab — run aggregations, inspect explain plans, paste results into a ticket.
Shell and grid share the same active connection; no second Compass window.

Query lab adapts to MongoDB with shell execution and formatted output. Engine-aware Pulse shows cluster context after connect.

Explore the full feature guide: MongoDB guide