What is MongoDB?
MongoDB is a data & databases tool. With OSP.net, your AI agent connects to it directly so it can act on your behalf instead of just answering questions about it.
What your OSP agent can do with MongoDB
- Explore databases, collections and schema
- Run read-only find queries and aggregations
- Summarize document shapes and counts
How to connect MongoDB
- Get your connection string. Atlas: Database → Connect → Drivers, and copy the mongodb+srv://… URI (fill in your user/password). MongoDB Docs: connection strings
- Strongly recommended: create a dedicated read-only database user (Atlas: Database Access → Add New Database User → built-in role "Only read any database") and use it in the string. MongoDB Atlas: database users & roles
- Paste the full connection string here and Connect. Your agent runs MongoDB's official MCP server in --readOnly mode no matter what. MongoDB Docs: MCP server
Security: Defense in depth: the agent always runs the MongoDB MCP server with --readOnly, so it can query and explore but never write — but the credential itself should still be least-privilege. Use a read-only user, and avoid your production primary if a secondary/analytics node exists.
Related data & databases integrations
Frequently asked questions
- Can OSP.net connect to MongoDB?
- Yes. MongoDB is a native OSP.net integration — you bring your own MongoDB key or token, paste it in your dashboard, and your agent restarts live.
- What can my OSP agent do with MongoDB?
- Your agent answers questions from your MongoDB database — read-only — via MongoDB's official MCP server. Specifically: Explore databases, collections and schema; Run read-only find queries and aggregations; Summarize document shapes and counts.
- Is MongoDB a native integration or via the gateway?
- MongoDB is a native, baked-in integration. You connect it with your own credentials, which are stored in an encrypted vault and injected only at runtime.
- Is my MongoDB data secure with OSP.net?
- Yes. Your MongoDB credentials live in an encrypted secrets vault, are injected only at container runtime, and are never written to disk in plaintext or used to train any model. Each customer runs in a fully isolated instance.