Integration · Database
MongoDB + OrchestrAI
Catalog exported 2026-09-02 · MongoDB website
Query and aggregate MongoDB in plain language, insert documents, and add indexes with confirmation.
OrchestrAI exposes 4 MongoDB operations: 2 are low-risk (read-only or low-impact), and 2 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.
What teams use it for
Ask for the twenty most recent orders with status pending in the orders collection, or for a group-by pipeline that counts signups per day, and OrchestrAI translates the request into a find or aggregation and returns the documents. Support engineers use it to insert a corrective document or seed test data, and to add an index once a slow query shows up, with the index build held for your approval. Coverage stops at reads, inserts, and indexes: there is no update, delete, or drop operation, so document edits and collection removal still happen in mongosh or Compass.
Every MongoDB operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
MongoDB Aggregation |
Run MongoDB aggregation pipeline | Low risk | No |
Query MongoDB |
Query MongoDB documents | Low risk | No |
Create MongoDB Index |
Create index on MongoDB collection | Creates resources | Yes |
Insert MongoDB Documents |
Insert documents into MongoDB | Creates resources | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
What you connect
A MongoDB credential (stored as mongodb).
Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Find users in the accounts collection who signed up in the last 7 days and have no email verified
- Run an aggregation on orders that groups by country and sums the total field for August
- Create a compound index on sessions for user_id and created_at descending
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI delete documents from MongoDB?
- No, The MongoDB operations available are query, aggregate, insert, and create index. Nothing in the set removes or modifies existing documents, which keeps the integration safe to hand to people who only need answers from the data.
- Will OrchestrAI build an index on a MongoDB collection without asking?
- No, mongodb_create_index is medium risk and marked confirm, so it shows you the collection and key specification and waits until you approve before the build starts.
- How does OrchestrAI authenticate to MongoDB?
- You add a MongoDB credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.