Compatibility answer · checked 2026-07-16

Does Cursor work with Neon MCP?

Conditional. The connection requirements intersect, with the listed availability or setup conditions. This is a reviewed requirements comparison, not a live integration, uptime, or security test.

Read the JSON receipt Compare all 90 pairs

Compatibility receipt

What the evidence supports

Direct means an official source names the pairing. Inferred means compatible documented requirements intersect, while every remaining condition stays visible.

Conditional

Current verdict

The connection requirements intersect, with the listed availability or setup conditions.

inferred

Evidence level

The documented transport and authentication requirements intersect, but the provider does not explicitly name the pairing.

2026-07-16

Observation date

Product behavior can change after this date. Check the linked provider guidance before production use.

Portable compatibility receipt

Embed this badge

Copy the Markdown below into a repository or document. The image reflects this reviewed catalog result and links back to the dated compatibility receipt.

markdown · /badges/compatibility/cursor/neon.svg

[![Cursor ↔ Neon MCP · Conditional · checked 2026-07-16](https://resolvemesh.com/badges/compatibility/cursor/neon.svg)](https://resolvemesh.com/compatibility/cursor/neon)

Requirements match

Transport, authentication, and remaining gates

The intersections below are computed from the reviewed client and tool profiles. Empty intersections remain explicit.

STREAMABLE_HTTP · STDIO

Matched transport

Client supports STREAMABLE_HTTP · SSE · STDIO. Tool requires STREAMABLE_HTTP · STDIO.

OAUTH_2_0 · BEARER_TOKEN

Matched authentication

Client supports OAUTH_2_1 · OAUTH_2_0 · BEARER_TOKEN · NONE. Tool requires OAUTH_2_0 · BEARER_TOKEN.

4 visible

Conditions and caveats

Neon recommends development and testing only and warns against connecting MCP agents to production databases.
The readonly=true parameter disables write operations; OAuth can also request a read-only scope.
The legacy SSE endpoint is deprecated and does not support API-key authentication.
Review and authorize actions before they run; an optional IP allowlist requires two static Neon IP addresses.

Reviewed profiles

Cursor and Neon MCP

ResolveMesh compares the documented connection surfaces. It never sends credentials to either provider from this page.

Client

Cursor

IDE MCP client supporting local stdio and remote SSE or Streamable HTTP connections.

Hosted tool

Neon MCP

Neon's hosted and local MCP server for database branches, migrations, and authentication configuration.

https://mcp.neon.tech/mcp

Compatibility change radar

Reviewed changes affecting this pair

Only approved events naming both this client and this tool appear here. The filtered JSON feed uses the same ledger.

No approved event

No pair-specific change is in the ledger

This means no reviewed event currently matches both records; it does not prove the providers have never changed.

GET /v1/compatibility-changes?client=cursor&tool=neon

Machine-readable change feed

Poll the filtered JSON feed for reviewed events affecting this exact pair.

Primary evidence

Official sources behind this answer

ResolveMesh links to the source owners and preserves the observation date. Recheck current documentation before changing a production integration.

Cursor: Model Context Protocol

Official documentation used to derive this compatibility receipt.

Read the primary source

Neon: Neon MCP Server

Official documentation used to derive this compatibility receipt.

Read the primary source

Founder-reviewed alerts

Request a watch for Cursor + Neon MCP

A request helps prioritize the first external watchers. It does not create an account, begin monitoring, promise an alert, or charge a card.