Data & Storage · Integration
MongoDB Atlas
Add MongoDB Atlas to your product for your customers, and give your AI agents governed access to it.
Embed a MongoDB Atlas integration so your product can read and write the data your customers already keep in their own managed cluster, instead of asking them to ship you a copy. Documents are schema-flexible and fields appear and disappear without notice, so field mapping is configuration per customer and a change on their side does not become a release on yours. fastn handles per-tenant credentials, network and database-user scoping, paginated reads and query throttling, so a large scan does not compete with the customer's own workload.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Atlas cluster so your product queries their collections in place.
Insert and update documents from your product, scoped to the database and collections the customer grants.
Map each customer's own document shape as configuration, because two clusters rarely look the same.
Keep reads paginated and throttled so an initial load does not degrade the customer's own application.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a scoped read-only query against the customer's cluster before it answers.
An agent inspects a collection's fields so it queries what actually exists rather than guessing.
An agent writes a document within governed permissions, with the write logged per tenant.
Example prompt
Find documents in the orders collection created this week with a failed status and summarise the common cause.
Set up MongoDB Atlas in 4 steps
- 01Open the MongoDB Atlas connector from your fastn dashboard.
- 02Have each customer supply their own Atlas connection details and a scoped database user, stored encrypted per tenant.
- 03Map the databases, collections and fields your product uses, then enable the actions you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the MongoDB Atlas integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a MongoDB Atlas integration without building it. Your customers connect their own MongoDB Atlas account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a MongoDB Atlas update is not your on-call problem.
- One integration serves your product and your agents. The same governed MongoDB Atlas connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
MongoDB
PostgreSQL
SupabaseOften used alongside
Tools the same teams tend to run next to MongoDB Atlas, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceMongoDB Atlas integration FAQ
How do I add a MongoDB Atlas integration to my product?
Enable the MongoDB Atlas connector in your fastn dashboard, then let each customer authenticate their own MongoDB Atlas account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no MongoDB Atlas client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own MongoDB Atlas account?
Yes. Every connection is scoped to the individual customer, so each authorises their own MongoDB Atlas account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this MongoDB Atlas integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a scoped read-only query against the customer's cluster before it answers.
Who maintains the MongoDB Atlas integration?
fastn does. When MongoDB Atlas changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the MongoDB Atlas integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large MongoDB Atlas reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the MongoDB Atlas integration?
A common starting point: connect their own Atlas cluster so your product queries their collections in place. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the MongoDB Atlas integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding MongoDB Atlas does not change your per-connector cost. You can start free with 3 connected accounts.
Add MongoDB Atlas to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.