MongoDB MCP Server vs Neon MCP Server

MongoDB MCP Server 60

The server is free and open source, and runs against any MongoDB with no signup, so 20 + 20 + 20. No payment protocol (0). Atlas itself is billed by MongoDB with public plan pricing. On 4 October the pricing page listed Free at $0 with 512 MB, Flex up to $30 a month and Dedicated from $56.94 a month.

Neon MCP Server 40

No x402, MPP or L402 (0). Per-unit prices are public, compute per CU-hour and storage per GB-month (20). Free plan with no card (20). A person signs up and authorises in a browser; the CLI can mint a key only after a login (0). 0 + 20 + 20 + 0 = 40.

MongoDB MCP Server 88

Scored as a local stdio package (it also runs over HTTP). Official npm package mongodb-mcp-server, 3.2.2 as the npm latest on 1 November, and a Docker image, with Node ^20.19.0 || ^22.13.0 || >= 24.0.0 stated in engines (20). CI runs unit and integration tests on Ubuntu, macOS and Windows with Node 22, plus Node 24 and 26 on Ubuntu, alongside accuracy and end-to-end suites. The latest Code Health runs on main concluded Success on 1 October per the 4 October check (run results weren't readable on 17 October or 1 November), and the test job is still marked continue-on-error in a clone on 1 November, so a failing test leg wouldn't fail the run. 20 of 25. Ten open issues on 1 November, five of them bug reports (#1269 OIDC connect, #1427 output schemas declared as draft-07, #1490 a false COLLSCAN on sharded clusters, #1540 space-separated --disabledTools values ignored, #1643 aggregations that keep running after a cancel), three of them labelled stale with no activity. Most issues opened since 20 October are newer requests (20). Semver with major versions for breaking changes. MongoDB's docs keep dated release notes, still ending at 3.0.5 of 1 October on 1 November and listing neither 3.1.0 nor 3.2.x. The GitHub v3.2.1 release (28 October) has full notes, including the maxTimeMS deprecation, but the v3.0.0 release body is still empty per the 4 October check, and 3.2.2 is on npm without a tag or release (13). Version 3.2.2 (15).

Neon MCP Server 72

Hosted reading. neonstatus.com on status.io with components per region, though no MCP component (20). The page shows only the last 30 days, three incidents, a partial disruption of monitoring data on 21 October (1 hour 22 minutes), slow compute starts in us-east-2 on 2 November (2 hours 14 minutes) and 26 minutes of console and API errors on 2 November; August and September weren't readable (15). The Neon API publishes 700 requests a minute with a 40-a-second burst per route (15). 429 with exponential backoff advice and 423 Locked for overlapping operations with retry guidance, but no idempotency keys (12). An uptime SLA on Scale only, with no percentage on the pricing page (5). The docs give the server no status label and the README says it isn't recommended for production (5). 20 + 15 + 15 + 12 + 5 + 5 = 72.

MongoDB MCP Server 94

npm latest 3.2.2 on 29 October 2026, after v3.2.1 on 28 October (30). Thirteen stable releases from v2.0.0 (published 4 August) through 3.2.2 in the 90 days to 1 November (20). Commits on main most days (23 since v3.1.0, the latest on 30 October), a stale bot that labels inactive issues, and ten open issues on 1 November, five opened since 20 October (20). Listed in the official MCP registry as io.github.mongodb-js/mongodb-mcp-server, a GitHub-verified namespace. After the 21 October fix to the publish step, the registry's latest entry on 1 November is 3.2.1, published 28 October, one patch behind npm's 3.2.2, so the 2 held back since 4 October for the stale 2.1.0 entry are restored (15). Dependabot, CodeQL and a dependency-health workflow, and releases upload an SBOM. The failed Docker release (#1312) was closed as not planned by the stale bot on 3 September without a fix, and 3.2.2 shipped a day after 3.2.1 because two library packages failed to import (9).

Neon MCP Server 80

v2.0.0 on 5 November 2026, one day before this check (30). 1.0.0 (registry, 17 September) and 2.0.0 in the 90 days, two releases (10). 53 open issues and pull requests, with commits most days; reply times weren't measured (15). com.neon/mcp in the official registry, a domain-verified namespace, at 2.0.0 (15). Unit, integration and end-to-end test suites, knip and lint in CI (10). 30 + 10 + 15 + 15 + 10 = 80.

MongoDB MCP Server 81

Database tools use a MongoDB user's own roles. Atlas tools use Atlas service accounts (client ID and secret) with per-operation roles listed in the README, connecting to an Atlas cluster creates a temporary database user that expires after 4 hours, and the managed server uses OAuth. Secrets can go on the command line, which the README warns against (25). --readOnly removes create, update and delete tools, --indexCheck rejects collection scans and server-side JavaScript is off by default. Confirmation is on by default for eight risky tools, but a client without elicitation runs them unconfirmed, and read-only isn't the default (18). Documents and query results come back wrapped in per-call UUID tags with a warning not to follow instructions inside them, on by default. Version 3.1.0 (15 October) adds --disableUntrustedDataWarning, default false, which returns results without the tags (13). Logs go to disk and to the MCP client by default, and Atlas keeps its own activity feed (10). MongoDB publishes a vulnerability disclosure policy, and its trust page lists ISO/IEC 27001:2022 and SOC reports for Atlas, per the 4 October check. The repository still has no SECURITY.md on 1 November ("This project has not set up a SECURITY.md file yet") and publishes no advisories, OSV listed none on 17 October, and mongodb.com/.well-known/security.txt answered with the site's HTML page, not a security.txt, per the 17 October check, not re-read on 1 November (15).

Neon MCP Server 69

OAuth 2.1 with read and write scopes, per-project and per-role fixed grants, Client ID Metadata Documents and RFC 9207 iss on redirects, or API keys (28). Read-only mode keeps SQL in READ ONLY transactions and withholds connection strings, roleName limits SQL to a role's grants, and destructive tools ask the model to confirm with the user; with an API key anyone who can edit the URL can widen the grant (17). The README warns to review every action and keep the server away from production, but we found no prompt-injection guidance for query results (5). Neon has project audit logs, but we didn't read whether MCP calls appear (5). SOC 2 Type II with a public SOC 3, ISO 27001 and 27701, HIPAA; no security.txt on neon.com (14). 28 + 17 + 5 + 5 + 14 = 69.

MongoDB MCP Server 81

Every tool takes a typed zod schema, and read tools such as find declare output schemas (25). MongoDB serves an llms.txt for the MCP server docs at mongodb.com/docs/mcp-server/llms.txt, live on 17 October and linked from the release notes page read on 1 November (10). Some descriptions say when to use them (list-connections says "Use this to find a connectionId established earlier", the streams tools list the requests they fit), but most database tools get one line ("Run a find query against a MongoDB collection"). Issues #1375 (66 parameters without descriptions) and #1402 (tools that confuse agents) are no longer in the open list on 1 November, and the README descriptions are unchanged since 17 October (12). Sort directions are enums and limit and responseBytesLimit have defaults. Filters and projections are free-form EJSON, which MQL needs (10). README and docs carry config examples. Errors come back as Error running <tool>: <message> with isError set (10). Semver, GitHub releases, dated release notes in the docs from 1.8.1 to 3.0.5 and a server.json for the registry (14, less 1 because the docs page still lists neither 3.1.0 nor 3.2.x on 1 November and 3.2.2 has no GitHub release).

Neon MCP Server 90

Every tool has a JSON Schema, many generated from the Neon OpenAPI spec (25). neon.com serves llms.txt and Markdown pages (10). Descriptions say when and when not ("branch_id is a branch id, not a branch name. Call list_branches to resolve a name", "NEVER run autonomously") (18). Typed inputs with enums such as access read_only or read_write, and path arguments checked for . and .. since 2.0.0 (13). Examples in the README and docs, and API 4xx errors classified by kind (11). CHANGELOG with dated releases and a registry version (13). 25 + 10 + 18 + 13 + 11 + 13 = 90.

MongoDB MCP Server 84

Apache-2.0 (30). The README says where logs and exports live, that exports expire after 5 minutes and that both may hold sensitive data, and MongoDB's privacy policy (last updated 4 November 2025) covers usage data from its products (22). Deprecated options are marked in the configuration table (connectionScope, healthCheckHost, and since 3.2.1 maxTimeMS and the two count caps in favour of timeoutMs) and Node 20 support is flagged for removal, but without dates (12). Telemetry is on by default and the README documents three opt-outs (MDB_MCP_TELEMETRY=disabled, --telemetry disabled, DO_NOT_TRACK=1). It says only "usage data". The source shows tool name, duration, result and a device id, and 3.1.0 fixes events emitted after close being dropped (15).

Neon MCP Server 75

MIT (30). Databricks' privacy notice (9 January 2026), the Neon product schedule (14 October 2026) with a DPA and a sub-contractor list linked from every page (24). The SSE retirement returns 410 with a pointer, and the stdio package is marked deprecated, but no notice period is stated (15). Telemetry is disclosed in the README, Segment identify with account ID, name and email plus every tool call, but hosted users have no opt-out (10). 30 + 24 + 15 + 10 = 79.