Microsoft published its official PostgreSQL extension to the Open VSX registry on June 1, 2026, the change that unblocks every Cursor user who has been stuck without first-party Postgres tooling since the extension shipped on the proprietary VS Code Marketplace last year. The release also adds a Model Context Protocol server, so Cursor's agent can introspect your database schema and read query plans without leaving the chat.

Try It: Wire Cursor's Agent Into a Live Postgres Database

The setup takes under five minutes on an existing project:

  1. In Cursor, open Extensions and search "PostgreSQL" by ms-ossdata. The Open VSX listing now resolves where the previous Marketplace install path used to fail.
  2. Click the new database icon in the activity bar. If you run Postgres in Docker, the extension auto-detects the container and offers a one-click connection. Otherwise, point it at a connection string.
  3. Open Cursor's agent panel and ask "what tables do we have and which ones look like they're missing indexes?" The DBAgent MCP server answers from live schema, not from an outdated README.
  4. For the query you are actually writing, hit the inline EXPLAIN button. The query plan renders as an interactive icicle chart with sequential scans flagged in red.

The agent integration is the unlock most teams will care about. Until today, getting Claude or GPT to write a correct migration meant pasting a schema dump into context every time. Now the agent reads it on demand.

Why It Matters

Cursor's marketshare among AI-native developers has been growing on the back of Claude Sonnet and Composer-1, but the editor inherited a real gap from upstream VS Code: Microsoft ships some extensions only to the Marketplace, not Open VSX, leaving forks without legal access. The Postgres extension was the most-requested missing piece, with a GitHub issue tracking the install failure for months. Microsoft cross-publishing to Open VSX, voluntarily, signals that the company sees Cursor as a distribution channel worth supporting rather than ignoring.

Key Details

  • MCP server bundled: The extension registers a DBAgent MCP server. Any agent that speaks MCP (Cursor, Claude Code, ChatGPT desktop) gets schema introspection and performance diagnostics as native tools.
  • Zero-config discovery: Detects .env files, docker-compose.yml services, and running local Postgres instances automatically.
  • Query plan visualizer: Interactive node graphs and icicle charts for EXPLAIN ANALYZE output. Click a node to see row estimates vs actuals.
  • Performance dashboard: Live database load, query activity, and wait-event tracking inside the editor.
  • SSH tunneling: Built-in tunnel support for databases on private VPCs, no external client needed.
  • License: Same MIT-licensed core as the GitHub repo. The Open VSX listing is the same binary as the VS Code Marketplace version.

What to Do Next

If you ship Postgres apps from Cursor, install the extension and configure the MCP server before your next migration. Live schema in the agent's context plus inline EXPLAIN diagnostics removes the two biggest sources of agent-written SQL bugs: stale table assumptions, and queries that pass tests but trigger sequential scans at production volume.