mongodb-mcp-server
This is an MCP server from the mongodb-js organization for working with MongoDB databases and MongoDB Atlas from an AI client. It needs Node.js 20.19 or newer (22.12 or newer on v22) and either a MongoDB connection string or Atlas API service-account credentials; the README says the server will not start unless one of them is configured.
The tool list is split into Atlas tools (list organizations, projects and clusters, inspect a cluster, manage access lists and database users, create a free cluster, read performance-advisor suggestions and alerts), Atlas Local tools (create, connect to and delete local deployments) and database tools. Atlas tools only appear when API credentials are set. Configuration comes from environment variables, command-line arguments or the MCP client config file, with proxy support, and a `disabledTools` option can turn off tool names, operation types or whole categories.
Every example in the README includes `--readOnly`, which blocks write operations until you remove it. It also recommends giving the Atlas service account only the permissions it needs, and passing secrets through environment variables rather than command-line arguments, which can show up in process lists. A section covers deployment on Azure. Install in Cursor or VS Code from the README badges, or run `npx -y mongodb-mcp-server@latest --readOnly`. This review is based on the README and repository data; we have not run it ourselves.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-19
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 28
- Latest release
- v3.1.1-pre.1 (2026-10-15)
- Open issues
- 27
- Recent issues with at least one comment
- 2/2
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #1540 [Bug]: Space-separated `--disabledTools` values are silently ignored since 1.3.0, and the second value becomes the connection target9 comments · 2026-09-18
- #1427 [Bug]: outputSchema declares draft-07 (inherited SDK default), making every tool unusable in Claude Code6 comments · 2026-08-12
- #1269 [Bug]: connect tool reports "Successfully connected" for OIDC before auth completes, hiding the device-flow URL + user code6 comments · 2026-06-21
- #829 Feature Request: Add `maxTimeMS` Configuration Option for Query Timeout4 comments · 2026-01-06
- #1396 Expose `collectProcessMetrics` as a CLI/env config option3 comments · 2026-07-27
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- Your data is in MongoDB or MongoDB Atlas, and you want the vendor-organisation server.
- You want to manage Atlas from the agent: the README lists clusters, database users, access lists, performance advisor and alerts.
- You want to disable risky tools: --readOnly and disabledTools can turn off tools, operation types or whole categories.
- You use SQL databases; this server is MongoDB-specific.
- You cannot run Node.js 20.19 or newer (22.12 or newer on v22).
- You plan to give Atlas credentials with broad permissions and drop --readOnly; the agent could then change or delete real data and cluster settings.
How it differs
vs mcp-toolbox★ 16.7kMCP Toolbox spans many database types; the MongoDB server goes deep on one, including Atlas administration. Pick by where your data lives.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!