The MongoDB Plugin for IntelliJ provides seamless integration with MongoDB deployments, whether they are local, containerized, or hosted on MongoDB Atlas (including those managed via atlascli
).
The plugin aims to enhance your development workflow with intelligent code autocompletion, valuable performance and correctness insights, and a dedicated query runner.
It supports Java queries written with the MongoDB Java Driver and Spring Data MongoDB Criteria.
- Effortless Connectivity: Connect your IDE directly to any MongoDB cluster using your Data Explorer using a user-friendly side panel.
- Intelligent Autocompletion: Get smart suggestions for database names, collection names, and field names as you type.
- Performance Insights: Analyze your project for potential performance bottlenecks and receive actionable index suggestions.
- Smart Type Checking: Validate your schema and ensure the correctness of your queries with intelligent type checking.
- Integrated Query Runner: Transform your Java queries into valid
mongosh
queries and execute them directly within your IDE.
To get more information about plugin features and usage, please visit the documentation.
You can report new bugs by creating a new issue either in JIRA or GitHub. Please include as much information as possible about your environment and include any relevant logs.
We are aware of a bug in Skiko, the rendering library used by Desktop Compose that doesn't fall back to software rendering when a GPU accelerated driver is not available. This should be fixed in version 0.1.0 so please update the plugin to the latest available version in the Marketplace.
If you are in the latest version, and it doesn't work for you, do the following:
- Open IntelliJ IDEA
- Go to the main menu and select Help | Edit Custom VM Options
- Add the following line to the end of the file:
-Dskiko.renderApi=SOFTWARE
- Save the file and restart IntelliJ IDEA
It might be related to using the software renderer in Skiko. To confirm this situation:
- Open IntelliJ IDEA
- Go to the main menu and select Help | Show log in Files
- Open the idea.log
- Search the following string:
Could not use GPU accelerated rendering
- If it's there, Skiko is using your CPU to render instead of the GPU.
In case the log line is not there, please share the entire log file in a bug report.
The plugin doesn't support yet all the possible query variants. Notable unsupported features are:
- Atlas Search and Atlas Vector Search queries
- $lookup queries
- $text queries
In case you think we should prioritise your query, or it's a bug, please fill a bug report with a sample query.