MongoDB
Administer MongoDB Atlas organizations, projects, clusters, users, networking, backups, and related cloud resources with an Atlas OAuth service account.
Verdict
Common use cases
- Debug slow queries during incident response
- Generate weekly collection growth reports
- Validate schema changes before deployment
- Check cluster performance metrics in standup
- Prototype aggregation pipelines with live data
Integration
- Vendor
- MongoDB
- Category
- other
- Auth
- OAUTH2
- Tools
- 50
- Composio slug
mongodb
Tools
- Accept Group Stream Vpc Peering Connection
Accept One Incoming VPC Peering Connection. Uses the MongoDB Atlas Administration API. Required Atlas roles: Organization Stream Processing Admin, Project Stream Processing Owner
- Acknowledge Group Alert
Acknowledge One Alert from One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Alerts Manager
- Add Group API Key
Assign One Organization API Key to One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Add Group Teams
Add Multiple Teams to One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Access Manager
- Add Group User Role
Add One Project Role to One MongoDB Cloud User. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Access Manager
- Add Group Users
Add One MongoDB Cloud User to One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Access Manager
- Add Org Team User
Add One MongoDB Cloud User to One Team. Uses the MongoDB Atlas Administration API. Required Atlas roles: Organization Owner
- Add Org User Role
Add One Organization Role to One MongoDB Cloud User. Uses the MongoDB Atlas Administration API. Required Atlas roles: Organization Owner
- Authorize Group Cloud Provider Access Role
Authorize One Cloud Provider Access Role. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Owner
- Cancel Group Cluster Backup Restore Job
Cancel One Restore Job for One Cluster. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Backup Export Operator, Project Backup Recovery Operator
- Create Ephemeral Cluster
Create One Ephemeral Atlas Cluster. Uses the MongoDB Atlas Administration API. Required Atlas roles: No specific Atlas role is documented.
- Create Federation Setting Connected Org Config Role Mapping
Create One Role Mapping in One Organization Configuration. Uses the MongoDB Atlas Administration API. Required Atlas role: Organization Owner.
- Create Federation Setting Identity Provider
Create One Identity Provider. Uses the MongoDB Atlas Administration API. Required Atlas role: Organization Owner.
- Create Group
Create One Project. Uses the MongoDB Atlas Administration API.
- Create Group Access List Entry
Add Entries to Project IP Access List. Uses the MongoDB Atlas Administration API. Required Atlas role: Project Network Access Manager.
- Create Group Ai Model API Key
Create New AI Model API Key. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Model Owner
- Create Group Alert Config
Create One Alert Configuration in One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Alerts Manager.
- Create Group API Key
Create and Assign One Organization API Key to One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Access Manager
- Create Group Backup Export Bucket
Create One Snapshot Export Bucket. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Backup Manager
- Create Group Backup Private Endpoint
Create One Object Storage Private Endpoint for Cloud Backups for One Cloud Provider in One Project. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Owner
- Create Group Cloud Provider Access
Create One Cloud Provider Access Role. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Owner
- Create Group Cluster
Create One Cluster in One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Cluster Creator.
- Create Group Cluster Backup Export
Create One Snapshot Export Job. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Backup Export Operator
- Create Group Cluster Backup Restore Job
Create One Restore Job of One Cluster. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Backup Export Operator, Project Backup Recovery Operator
- Create Group Cluster Collection Restore Job
Create One Collection Restore Job. Uses the MongoDB Atlas Administration API.; required Atlas role(s): Project Backup Recovery Operator
- Create Group Cluster Global Write Custom Zone Mapping
Add One Custom Zone Mapping to One Global Cluster. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Cluster Global Write Managed Namespace
Create One Managed Namespace in One Global Cluster. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Data Access Admin
- Create Group Cluster Index Rolling Index
Create One Rolling Index. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Data Access Admin, Project Index Manager
- Create Group Cluster Online Archive
Create One Online Archive. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Data Access Admin
- Create Group Cluster Overload Simulation
Create One Overload Protection Simulation. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Cluster Manager
- Create Group Cluster Search Deployment
Create Search Nodes. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Cluster Search Index
Create One Atlas Search Index. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Search Index Editor
- Create Group Container
Create One Network Peering Container. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Custom Db Role Role
Create One Custom Role. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Database Access Admin, Project Stream Processing Owner
- Create Group Database User
Create One Database User in One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Database Access Admin, Project Stream Processing Owner
- Create Group Database User Cert
Create One X.509 Certificate for One Database User. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Data Federation
Create One Federated Database Instance in One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Encryption At Rest Private Endpoint
Create One Private Endpoint for Encryption at Rest Using Customer Key Management for One Cloud Provider in One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Flex Cluster
Create One Flex Cluster in One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Flex Cluster Backup Restore Job
Create One Restore Job for One Flex Cluster. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Backup Recovery Operator
- Create Group Integration
Create One Third-Party Service Integration. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Live Migration
Create One Migration for One Local Managed Cluster to MongoDB Atlas. Uses the MongoDB Atlas Administration API. Required Atlas roles: Organization Owner
- Create Group Log Integration
Create One Log Integration. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group MCP Config
Create One MCP Configuration for One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group MCP Config Secret
Create One Secret for One Project MCP Configuration. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
- Create Group Metric Integration
Create One Metric Integration. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner.
- Create Group Peer
Create One Network Peering Connection. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Network Access Manager
- Create Group Private Endpoint Endpoint Service
Create One Private Endpoint Service for One Provider. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner.
- Create Group Private Endpoint Endpoint Service Endpoint
Create One Private Endpoint for One Provider. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner.
- Create Group Private Network Setting Endpoint Id
Create One Federated Database Instance and Online Archive Private Endpoint for One Project. Uses the MongoDB Atlas Administration API. Required Atlas roles: Project Owner
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the MCP Integrations page. 2. Click 'Add Integration' and select MongoDB Atlas from the developer tools category. 3. In a separate tab, log into your MongoDB Atlas account and navigate to Organization Access Manager, then API Keys. 4. Create a new API key with Project Read Only permissions (or broader if you need write access), copy the public and private key pair immediately. 5. Return to Switchy and paste both keys into the connection form, then specify your Atlas project ID from the project settings page. 6. Click 'Connect' and wait for Switchy to verify the credentials against the Atlas API. 7. Open any Space and type '@MongoDB Atlas list my clusters' to confirm the connection works and see your available databases.
What teammates see: by default, memories from MongoDB are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Clusters
@MongoDB Atlas show me all clusters in this project with their configuration and current status
Query Collection Sample
@MongoDB Atlas get the 10 most recent documents from the users collection in the production database
Check Cluster Metrics
@MongoDB Atlas what are the current performance metrics for the primary cluster over the last hour
Inspect Database Schema
@MongoDB Atlas describe the schema and indexes for all collections in the analytics database
Run Aggregation Pipeline
@MongoDB Atlas run an aggregation on the orders collection to count total sales by product category this month
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@MongoDB-Atlas show me the current connection count and memory usage for the production cluster over the last hour
Based on the metrics from your production cluster, average connection count was 847 over the last hour, peaking at 1,203 around 14:32 UTC. Memory usage held steady at 68% of allocated capacity (13.6 GB of 20 GB). No connection pool saturation events detected. The cluster is running MongoDB 7.0.4 across three nodes in us-east-1.
This example demonstrates real-time cluster monitoring. Requires API key with 'Project Read Only' or higher permissions. Metrics granularity depends on your Atlas tier — M10+ clusters provide minute-level data, while M0/M2/M5 free tiers offer hourly aggregates only.
@MongoDB-Atlas create a new database user 'analytics_readonly' with read access to the 'events' database, restrict connections to IP 203.0.113.45
Created database user 'analytics_readonly' with read-only role on the 'events' database. IP whitelist entry added for 203.0.113.45. The user can authenticate immediately, but note that Atlas propagates IP whitelist changes across replica set members within 2-5 minutes. Temporary password: [generated]. You'll need to share this securely with the user and prompt them to rotate it on first login.
This write operation modifies cluster access control. Requires 'Project Owner' or 'Organization Owner' API key. Be cautious with IP whitelisting — overly permissive rules create security exposure. Atlas does not support password rotation reminders, so document the credential handoff process separately.
@MongoDB-Atlas analyze the slow query log from the last 24 hours and suggest three indexes that would improve performance
Reviewed 1,847 slow queries (>100ms) from the past 24 hours. Three high-impact index recommendations: (1) Compound index on 'users.email' + 'users.status' would accelerate 412 login-related queries, reducing average execution time from 340ms to ~15ms. (2) Index on 'orders.created_at' with descending sort would optimize the dashboard's recent-orders view, currently scanning 2.3M documents. (3) Partial index on 'sessions.expires_at' where expires_at > now() would shrink the active-session lookup from 890ms to sub-50ms. Estimated total write-throughput cost: +8% during index builds.
This synthesis example pairs Atlas's performance metrics with AI reasoning to prioritize optimizations. The MCP provides raw query stats; the AI interprets patterns and trade-offs. Index recommendations assume typical workload distribution — always test in staging before applying to production, as index builds lock collections on older MongoDB versions.
Use-case deep-dives
When MongoDB Atlas MCP fits rapid prototyping cycles
A 3-person backend team shipping a new feature every two weeks needs to inspect collections, test queries, and validate indexes without leaving their AI workspace. The MongoDB Atlas MCP works here if the team already uses Atlas and wants to skip context-switching to Compass or the web console. API key auth means each developer can scope their own credentials to read-only or specific databases. The trade-off: if your team runs self-hosted MongoDB or needs to write data frequently, this MCP won't help—it's read-heavy by design. If you're prototyping schema changes and want to ask "show me the last 50 user records with this field" in plain English, this MCP saves 4-5 tab switches per day. Worth it for teams that live in Switchy and treat Atlas as their primary datastore.
How support teams query production data safely
A 6-person support team fields 40 tickets a day, many requiring lookups in the production MongoDB cluster to confirm order status or user account details. The MongoDB Atlas MCP lets support reps ask natural-language questions like "find all orders for user ID 12345 in the last 30 days" without SQL knowledge or direct database access. API key scoping ensures each rep sees only the collections they need—no accidental writes, no access to sensitive admin tables. The boundary: if your support workflow already uses a purpose-built admin panel or if queries need to join across multiple databases, the MCP adds friction instead of removing it. For teams where 80% of lookups are single-collection reads and the alternative is Slacking an engineer, this MCP cuts median response time by 10 minutes per ticket.
When founders need ad-hoc metrics without a BI tool
A 2-person founding team at a pre-seed startup tracks user growth in MongoDB Atlas but hasn't built dashboards yet. The MCP lets them ask "how many signups this week" or "show me users who haven't logged in for 30 days" during weekly planning without writing aggregation pipelines or spinning up Metabase. API key auth means both founders share one read-only credential scoped to the analytics database. The limit: once you're running the same query daily or need visualizations, you've outgrown this pattern—build the dashboard. For the first 6 months when metrics questions are exploratory and change every week, this MCP keeps velocity high and tool sprawl low. If you're asking different questions every planning session, this beats maintaining a BI stack you'll replace in Q3.
Frequently asked
What does the MongoDB Atlas MCP do in Switchy?
It connects your Switchy workspace to MongoDB Atlas clusters so your team can query databases, inspect collections, and run aggregations directly from AI conversations. You skip context-switching between the Atlas UI and your chat threads. The MCP uses your Atlas API key to authenticate, so it inherits whatever cluster and project permissions that key holds.
Do I need admin access to connect MongoDB Atlas?
You need an Atlas API key with at least read permissions on the projects and clusters you want to query. Organization-level admin isn't required, but the key must be scoped to the specific projects your team needs. Generate the key in Atlas under Access Manager, then paste it into Switchy's connection flow.
Can the MCP write data or only read from MongoDB?
That depends on the permissions you grant the API key. If the key has write access, the MCP can insert, update, and delete documents. If you scope it to read-only, queries and aggregations work but mutations don't. Start with read-only until your team needs write operations.
Why use this instead of the Atlas UI or Compass?
The MCP keeps database work inside your AI workflow. Instead of copying a query result from Compass into a chat, you ask the question and get the answer in one step. It's faster for exploratory queries and debugging, though you'll still use the Atlas UI for cluster configuration and index management.
Who on the team should connect the MongoDB Atlas MCP?
Whoever manages your Atlas projects and can generate API keys. That's usually a backend engineer or DevOps lead. Once connected, anyone in the Switchy workspace can query the databases the key permits, so coordinate on access scope before you plug it in.