mongodb-connection
mongodb connection
What it does
- Connection pooling exists because establishing a MongoDB connection is expensive (TCP + TLS + auth = 50-500ms). Without pooling, every operation pays this cost.
- Synchronous (PyMongo, Java sync): Thread blocks; pool size often matches thread pool size
- Asynchronous (Node.js, Motor): Non-blocking I/O; smaller pools suffice
- Pools are created per server per MongoClient.
- Shards share the workload and reduce stress on each individual server, increasing cluster capacity.
- Create client once only and reuse across application (in serverless, initialize outside handler)
- Don't manually close connections unless shutting down
Requirements & configuration
- Each connection requires ~1 MB of physical RAM, so you may find that the optimal value for this parameter is also informed by the resource footprint of your application's workload.
- Make use of timeouts to keep only the required connections ready as per your workload's needs
- Use default max pool size (100) unless you have specific needs (see scenarios below)
- If the user requires help to troubleshoot connection issues, determine whether this is a client config issue or infrastructure problem.
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
mongodb-connection FAQ
What does the mongodb-connection skill do?
Optimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported driver language. Use this skill when working/updating/reviewing on functions that instantiate or configure a MongoDB client (eg, when calling `connect()`), configuring connection pools, troubleshooting connection errors (ECONNREFUSED, timeouts, pool exhaustion), optimizing performance issues related to connections. This includes scenarios like building serverless functions with MongoDB, creating API endpoints that use MongoDB, optimizing high-traffic MongoDB applications, creating long-running tasks and concurrency, or debugging connection-related failures. Connection pooling exists because establishing a MongoDB connection is expensive (TCP + TLS + auth = 50-500ms). Without pooling, every operation pays this cost. Synchronous (PyMongo, Java sync): Thread blocks; pool size often matches thread pool size
What does mongodb-connection require?
Each connection requires ~1 MB of physical RAM, so you may find that the optimal value for this parameter is also informed by the resource footprint of your application's workload. Make use of timeouts to keep only the required connections ready as per your workload's needs Use default max pool size (100) unless you have specific needs (see scenarios below) If the user requires help to troubleshoot connection issues, determine whether this is a client config issue or infrastructure problem.
How do I install mongodb-connection?
Run: npx -y skills add https://github.com/mongodb/agent-skills --skill mongodb-connection --agent claude-code — the source lives at github.com/mongodb/agent-skills.
Maintain mongodb-connection?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[mongodb-connection on getagentictools](https://getagentictools.com/skills/mongodb-agent-skills-mongodb-connection?ref=badge) npx agentictools info skills/mongodb-agent-skills-mongodb-connection The second line is the CLI lookup for this page — handy in READMEs and docs.
