# Reported issues for mongodb-mcp-server Pod holds 7 of 7 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects. Back to [mongodb-mcp-server](/mcp/mongodb-mcp-server). ## Most discussed ### [Bug]: Space-separated `--disabledTools` values are silently ignored since 1.3.0, and the second value becomes the connection target ### Version Reproduced on 3.0.2, 2.1.1, 2.0.0, 1.8.0, 1.6.0, 1.5.0, 1.3.1 and 1.3.0. Works correctly on 1.2.0 and earlier, so this looks like a regression in 1.3.0. ### App - [ ] Cursor - [ ] Windsurf - [ ] VSCode - [ ] VSCode Insiders - [ ] Claude Desktop - [x] Other ### Affected Models (if applicable) - [ ] Claude 3.5 Sonnet - [ ] Claude 3.7 Sonnet - [ ] GPT-4a - [ ] o4-mini - [x] Other ### Bug Description The README and the [Enable or Disable MCP Server Features… [Read the thread](https://github.com/mongodb-js/mongodb-mcp-server/issues/1540) · 2026-09-18 · open · external user · 9 comments ### [Bug]: connect tool reports "Successfully connected" for OIDC before auth completes, hiding the device-flow URL + user code **Version:** `main` (@ `9ed2d09`); code references below are from `main`. **App:** Other (Claude Code, via MCP) ### Bug Description When connecting with a `MONGODB-OIDC` connection string that uses the device-authorization flow, the `connect` tool returns `"Successfully connected to MongoDB."` even though authentication has **not** happened yet. The device-flow verification URL and user code never appear in the `connect` response. They only surface later, when the first data operation (e.g.… [Read the thread](https://github.com/mongodb-js/mongodb-mcp-server/issues/1269) · 2026-06-21 · open · outside contributor · 6 comments ### [Bug]: outputSchema declares draft-07 (inherited SDK default), making every tool unusable in Claude Code ### Version 2.1.0 (also reproduced on 2.0.0 and 1.14.0) ### App - [x] Other — Claude Desktop / Claude Code (macOS), app version 1.28929.0 ### Affected Models (if applicable) - [x] Other — model-independent; fails before any model is involved ### Bug Description **Every tool on this server is currently unusable in Claude Code / Claude Desktop.** `find`, `count`, `aggregate`, and `list-collections` all fail identically, at tool-registration time, before any request reaches the server… [Read the thread](https://github.com/mongodb-js/mongodb-mcp-server/issues/1427) · 2026-08-12 · open · external user · 5 comments ### [Bug]: All Atlas tools fail with "TypeError: Invalid URL" since 3.0.0 (node-fetch receives a platform Request) ### Version 3.0.3 (also 3.0.0–3.0.2; 2.1.1 works on the same machine and config) ### App - [x] Other: Claude Code (stdio transport) ### Affected Models (if applicable) - [x] Other: not model-specific ### Bug Description Every Atlas API tool of the local server fails with `TypeError: Invalid URL` before any request reaches the network: `atlas-list-clusters`, `atlas-inspect-cluster`, `atlas-connect-cluster` (logged as `Error adding IP access list: Invalid URL`, then `error inspecting… [Read the thread](https://github.com/mongodb-js/mongodb-mcp-server/issues/1553) · 2026-09-19 · closed · external user · 4 comments ### [Bug]: stdio server does not exit after stdin EOF, leaving orphaned processes ### Version 1.13.0 Environment: - Node.js 22.23.2 - npm 10.9.8 - Codex CLI 0.153.4 - ChatGPT desktop 26.903.71938 - macOS 26.6.2 (25G83) - stdio transport - `--readOnly` ### App - [x] Other: Codex / ChatGPT desktop ### Affected Models (if applicable) Not applicable. The behaviour occurs at the stdio process-lifecycle level. ### Bug Description When `mongodb-mcp-server` runs over stdio, it does not terminate after stdin reaches EOF. This leaves MongoDB MCP processes running after the… [Read the thread](https://github.com/mongodb-js/mongodb-mcp-server/issues/1515) · 2026-09-10 · closed · outside contributor · 4 comments ### [Bug]: `connectionName` is missing from the `list-connections` text output, though it is present in structuredContent ### Version Reproduced on 3.0.3 and 3.0.2. ### App - [ ] Cursor - [ ] Windsurf - [ ] VSCode - [ ] VSCode Insiders - [ ] Claude Desktop - [x] Other ### Affected Models (if applicable) - [ ] Claude 3.5 Sonnet - [ ] Claude 3.7 Sonnet - [ ] GPT-4a - [ ] o4-mini - [x] Other ### Bug Description ### Bug Description `connect` accepts an optional `connectionName`, described in its own input schema as: ``` Optional short label for the connection (stored slugified with a short suffix, e.g.… [Read the thread](https://github.com/mongodb-js/mongodb-mcp-server/issues/1576) · 2026-09-28 · open · external user · 2 comments ### Expose `collectProcessMetrics` as a CLI/env config option ### Summary `@mongodb-js/mcp-metrics` already supports Node.js/process metrics via `PrometheusMetricsOptions.collectProcessMetrics`, but there is no way to enable it when running the published server (CLI or Docker image). Only library consumers who construct their own `PrometheusMetrics` can turn it on. Result: an HTTP-transport deployment scraping `/metrics` gets the three MCP metrics but **no** heap, GC, event-loop-lag, or file-descriptor metrics for what is a long-running Node process.… [Read the thread](https://github.com/mongodb-js/mongodb-mcp-server/issues/1396) · 2026-07-27 · open · external user · 2 comments ## Most recent The remaining reports are on [the project's issue tracker](https://github.com/mongodb-js/mongodb-mcp-server/issues).