What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

As a DevOps engineer managing multiple environments (dev, QA, staging, production) across several applications, the number of saved connections grows quickly. Currently, all connections are listed flatly in MongoDB Compass, making it difficult to locate, organize, and manage them efficiently. This leads to confusion, slower workflows, and increased risk of connecting to the wrong database.

What would you like to see happen?

Describe the desired outcome or enhancement.

I would like MongoDB Compass to support grouping and organizing saved connections into folders or categories (e.g., by application, environment, or team). These groups should be expandable/collapsible and optionally support features like archiving, tagging, or pinning frequently used connections.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

This enhancement would significantly improve productivity, especially in environments where teams manage many databases. It reduces cognitive load, minimizes operational mistakes (like connecting to production unintentionally), and aligns with best practices for environment separation and access management. It also makes onboarding easier for new team members.

What steps, if any, are you taking today to manage this problem?

Currently, we rely on manual naming conventions (e.g., prefixes like PROD_, DEV_, QA_) to differentiate connections. In some cases, we limit saved connections or maintain external documentation to track them. However, these are workarounds and not scalable as the number of services and databases increases.