Reference · built on requestConnectorDatabases & warehouses

MongoDB

Documents from MongoDB collections and change events from change streams, over the MongoDB Wire Protocol on port 27017.

Request accessPricing ↗

About

MongoDB is a document database from MongoDB, run self-managed as Community Edition or Enterprise Advanced, or as MongoDB Atlas. Drivers talk to mongod and mongos over the MongoDB Wire Protocol, a request-response protocol over TCP on port 27017 that carries OP_MSG and OP_COMPRESSED messages. Replica sets and sharded clusters on the WiredTiger storage engine expose change streams, opened with db.collection.watch(), db.watch(), or Mongo.watch(), which report data changes once they have persisted to a majority of data-bearing members. Atlas adds an Administration API for projects, clusters, and database users; it does not read cluster data.

An operator on Fibric reads the collections you grant, follows a change stream from a saved resume token, and proposes document changes for your approval, each with a receipt and an undo.

This is a reference listing. It documents what Fibric would read from MongoDB and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Documents from collections the database user can read, granted by the read role, which carries find and listCollections
  • Change events from db.collection.watch(), db.watch(), or Mongo.watch() on a replica set or sharded cluster
  • Resume tokens on each event, replayed with resumeAfter or startAfter while the oplog still holds the position
  • Collection and index metadata through listCollections and listIndexes
  • Cluster, project, and database user records from the Atlas Administration API v2

Proposed actions

  • Target capability: propose inserting or updating a document in a named collection, which needs the readWrite role
  • Target capability: propose a database user change through the Atlas Administration API, shown in full before it is sent

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Watch order documents as they change

    Open a change stream on the orders collection and react to status updates within moments of the write, without polling the collection on a schedule.

    With Order Risk, Data Freshness

  • Explain a metric from the documents behind it

    When a figure moves, query the collections by _id or a date field and show the reviewer the documents that produced the number.

    With Metric Reconciliation, Operations Analyst

  • Prove the stream is still flowing

    Track the resume token's cluster time against the clock and flag a stream that stalls, closes on an invalidate event, or loses its oplog position.

    With Integration Health

Requirements

  • A replica set or sharded cluster on WiredTiger, since standalone deployments do not open change streams
  • A database user with the read role, which includes the changeStream and find actions on non-system collections
  • Network reach to mongod or mongos on port 27017, or your configured port, over TLS
  • For Atlas management, a service account with a client ID and secret scoped to the project
Authentication
A database user authenticated with SCRAM, the default mechanism, or X.509; the Atlas Administration API uses a service account with OAuth 2.0 client credentials, whose access tokens last 1 hour.

Limits

  • Change streams resume only while the oplog still holds the token's position; a purged oplog means a fresh full read
  • A collection drop or rename sends an invalidate event and closes the stream; resumeAfter cannot continue past it
  • Time series collections do not support change streams
  • Atlas Administration API requests are rate limited by token bucket and return 429 when exhausted; the limits can change without notice

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request MongoDB ↗

Questions and answers

Does the connector need a replica set?
Yes for change streams. MongoDB documents change streams for replica sets and sharded clusters using WiredTiger and replica set protocol version 1. A standalone mongod can still be read by query, but it emits no change events.
What privileges does a change stream need?
The changeStream and find actions on the collection, database, or deployment being watched. The built-in read role grants both, along with listCollections and listIndexes, on all non-system collections in its database.
Can the Atlas Administration API read my data?
No. It manages projects, clusters, and database users, and MongoDB states it does not provide access to the data stored in clusters. Reading documents needs a database user connecting over the wire protocol.
Ask about MongoDB

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with MongoDB through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy