MongoDB Atlas API Skill
Overview
The Atlas Administration API allows you to programmatically manage clusters, database users, and network peering.
Installation
# Standard fetch/axios is used for REST API
Authentication
Atlas uses HTTP Digest Authentication. You must generate Programmatic API Keys (Public and Private keys).
Core Concepts
- Project: A logical grouping of clusters.
- Cluster: A MongoDB deployment.
- IP Access List: Network security firewall rules.
Common Workflows
- Generate API Keys in the Atlas UI.
- Perform an HTTP Digest Auth request.
- Provision or scale a cluster.
Error Handling
Handle HTTP 401 for Auth failures. For HTTP 400s, parse the detail property in the JSON response to understand the specific validation error.
Security
Restrict Programmatic API keys to specific IP addresses. Assign the 'Project Read Only' role unless mutation is explicitly required.
Rate Limits
Atlas API is limited to 100 requests per minute per project.
Best Practices
Automate IP Access List management if your deployment environment (like GitHub Actions) uses dynamic IP ranges.
Troubleshooting
If requests fail with 401 Unauthorized, ensure your HTTP client properly implements the Digest Auth handshake (which requires two round trips).
References
Why use this skill
Use this when your agent works with mongodb-atlas — structured patterns beat pasted docs and prevent common hallucinations.
AI pitfalls
- Inventing column names or schema fields
- Using deprecated driver methods or wrong connection strings
- Omitting connection pooling or transaction boundaries
Production checklist
- Migrations version-controlled and applied via CI
- Connection limits and pooling configured
- Backups and restore procedure documented
Related skills
prisma— integrates with
Last Verified: 2026-07-02