Databases
MongoDB Atlas integration
Connect your MongoDB Atlas cluster read-only and chart its collections as live dashboards in minutes.
Flitch is an AI BI tool that connects to MongoDB Atlas and turns your tables into shareable dashboards. Point Flitch at your managed Atlas cluster, choose the collections you want, and it flattens their nested documents into tidy rows. Then describe the product analytics, engagement or revenue view you need in plain language and let scheduled refresh do the rest.
- Connect your Atlas cluster read-only
- Pick collections to import as datasets
- Documents flattened into rows automatically
How do you connect MongoDB Atlas to Flitch?
Connect securely with your database credentials. Flitch only needs read access.
Generate a dashboard
Pick a prompt to get started.
MongoDB Atlas integration FAQ
How do I connect MongoDB Atlas to Flitch?
Use your cluster's SRV connection string (mongodb+srv://) with a database user that has read access, then choose the collections to import.
Do I need to change my Atlas network access settings?
Yes. Add Flitch to your Atlas IP access list so the cluster accepts the connection. A read-only database user is all it needs, no admin rights.
Can I connect one Atlas database instead of the whole cluster?
Yes. Point Flitch at the database you care about and select just those collections. Each becomes its own dataset and the rest is left untouched.
How does Flitch turn Atlas documents into charts?
It unpacks nested document fields into columns as it imports, so an Atlas collection becomes a table you can group, filter, and chart without any prep.
Does connecting Atlas give Flitch write access?
No. The database user you create is read-only, so Flitch reads only the collections you pick and never modifies your Atlas data.
Does Flitch copy my MongoDB Atlas data?
No. Flitch queries MongoDB Atlas where it sits and pushes the aggregation down as SQL, so it reads back totals rather than holding a copy of your tables. Nothing to keep in step, nothing extra to secure, and a large table stays your database's problem rather than something Flitch has to store. The queries are generated against your data model, so a figure means the same thing on every dashboard built from it.
More in Databases
Not the source you're after?