Availability
The MongoDB connector is available under SOCK → Sources → Add source → Connect System. It supports and is certified for MongoDB 7.
| Property | Current behaviour |
|---|---|
| Execution | Desktop |
| Identity | The signed-in member's MongoDB credential |
| Secret storage | Operating-system credential store, scoped to the member |
| Direction | Read-only; MSOCK writes nothing to MongoDB |
| Operation timeout | 15 seconds per operation |
| Bounded read cap | 10,000 rows/documents |
| Sample cap | 200 rows/documents |
Connection fields
Provide a MongoDB connection string. It is the secret and carries the addressing and TLS parameters supported by your MongoDB deployment. The database field is optional: leave it blank to list every database the credential can access, or provide one to narrow discovery.
Select the evidence scope
Browse the databases and collections visible to the member's credential. Select only what belongs in this harness, then decide whether bounded samples are permitted by your data policy.
Extraction uses a bounded worker pool and reads collection structure and samples. It does not insert, update, or delete documents.
Version and readiness checks
A server below MongoDB 7 is refused before harness files are written. A server above the certified range is captured with an uncertified-version warning in the manifest rather than being presented as a Known Unknown. If the local driver is unavailable, repair that prerequisite and retry.