MongoDB's mongodb-mcp-server 2.0.0 removes session state and requires explicit connection ids

MongoDB published mongodb-mcp-server v2.0.0 on August 4, a major release that removes session state from the server. Database operations now require an explicit connection id: the connect, atlas-connect-cluster, and atlas-local-connect-deployment tools return a connection id for subsequent calls, and a pre-configured connection uses the hardcoded preconfigured id. The changelog entry records the change as "remove session state and add explicit connection management" (MCP-601, PR #1361).

The release tightens input handling in the same pass: unrecognized tool arguments are now rejected via strict input validation (MCP-602), and atlas-create-project requires projectName and orgId. On the Atlas side, atlas-create-cluster gains customer-managed-key and multi-region support, existing clusters get pause, resume, and upgrade tooling, and Atlas Search aggregation pipelines gain $rerank support. A fix validating streams resourceName and peeringId blocks a path traversal (STREAMS-2485). The release ships an mongodb-mcp-server-2.0.0.mcpb bundle asset.

A discipline point for the tracker: the release notes name no MCP spec revision. The session-state removal is consistent with the ecosystem's stateless direction, but the notes do not state 2026-07-28 conformance, so no spec-support record follows from this evidence alone.