The editor knows it’s prod
Tag a connection prod, staging or dev. NexQL tints the chrome and badges the status bar, so you can’t mistake one for another.
status bar: ● PRODUCTIONExplorer, SQL notebooks, a live dashboard and an AI assistant that reads your schema, in the VS Code window you already have open. No second app, no second window.
# VS Code: Ctrl+P, then paste
ext install ric-v.postgres-explorerAdd a connection in the sidebar, give it a name and an environment, and go. The status bar always shows where you are.
New connection
A tree explorer for the catalog, and native .pgsql notebooks for the queries. Each cell keeps its own results.

NexQL Bot reads your live catalog before it writes anything, and shows which objects it looked at. The SQL lands in a notebook cell. Nothing runs until you press play.
Pick a question
Safe by default. Generated SQL lands in a notebook cell. Auto-LIMIT caps runaway SELECTs, and writes against a prod-tagged connection need explicit confirmation.
NexQL Free AI is the default: no key, no account. Or add your own. Each key is kept in OS-encrypted storage.
A live dashboard inside VS Code. Activity, locks, WAL and checkpointer stats, bloat, autovacuum progress and unused indexes, refreshed in place.

Tag a connection prod and NexQL tints the editor, badges the status bar and scores every statement before it runs.
Tag a connection prod, staging or dev. NexQL tints the chrome and badges the status bar, so you can’t mistake one for another.
status bar: ● PRODUCTIONDELETE without WHERE, TRUNCATE and DROP open a scored dialog with Execute, Transaction or Cancel. On prod connections the score is multiplied.
DELETE without WHERE → high riskA write against a prod connection needs an explicit confirmation. Nothing from the assistant runs on its own either.
Confirm: UPDATE on PROD?Turn on read-only for a connection and writes are blocked. SELECTs still get an automatic LIMIT, configurable per workspace.
auto-LIMIT 1000That’s a day with NexQL. Want to click around first?
This is the NexQL workbench running on sample data: the explorer, a notebook, the SQL assistant and the status bar. It never connects to a real database. Pick any of the 39 editor themes from the bar above the window.
Prefer your own palette? Browse all 39 themes ↗
MCP server
NexQL bundles the nexql-mcp server and registers it in VS Code over stdio. There are no URLs, ports or tokens to paste: your connections just show up.
55 tools · stdio · changes off by default
Agents search a live, indexed copy of your catalog and follow foreign keys, so they stop guessing table names.
orientsearch_schemadescribe_objectget_join_path
Every query runs in a read-only transaction. Statements that change data are refused unless you switch changes on.
run_selectexplain_queryexport_query
Blocking locks, the slowest statements, unused indexes and a one-call health check, without opening a dashboard.
find_blocking_locksslow_queriessuggest_indexesdb_health_check
Diff two schemas, draft the migration, and check the DDL for dangerous locks. Nothing is applied by the review.
schema_diffgenerate_migrationcheck_ddl_safety
Tested against PostgreSQL 12–17 every release, with version-gated fallbacks for managed platforms.
Compare
How NexQL in VS Code stacks up against the desktop clients you may be using today.
| Capability | NexQL | pgAdmin | DBeaver | TablePlus |
|---|---|---|---|---|
| Lives in VS Code | Native | No | No | No |
| SQL notebooks | Interactive .pgsql | No | No | No |
| AI assistant | Built in, schema-grounded | No | No | No |
| MCP server for agents | Bundled binary | No | No | No |
| Real-time dashboard | Yes | Yes | Limited | Limited |
| In-grid editing | Yes, explicit commit | Yes | Yes | Yes |
| Export formats | CSV, JSON, Excel | CSV, JSON | CSV, JSON, Excel | CSV, JSON, SQL |
| Foreign data wrappers | Full management | Yes | Limited | No |
| License | MIT core | PostgreSQL | Apache 2.0 | Proprietary |
Pricing
Import, backup, indexing, notebooks and the AI assistant are unlimited on every tier. Subscriptions fund the work and lift the AI token ceiling.
$0 forever
Everything you need to run a database from your editor.
Install from Marketplace$2/month
For the developer who lives in NexQL and wants the sharper model.
$9/month
One flat licence covering a team of up to five developers.
Paid checkout is temporarily unavailable. Free is not affected.
After checkout you get a license key. Click Activate in VS Code, or run NexQL: Activate License from the command palette. Already subscribed?Manage or cancel your subscription.
By subscribing you agree to our Terms of Service andPrivacy Policy.
Open core
The core builds a fully working free extension that anyone may fork, rebrand and publish. Stable releases ship from version tags. A nightly pre-release publishes on every merge to main.
Pre-release build carrying the v2.4.0 feature set — NexQL Bot rebrand, MCP install/update UX, agentic step limits, and notebook context fixes.
SQL Assistant is now NexQL Bot. MCP gets one-click install, update checks, and tool profiles in Preferences. Agentic step limits, scratch-notebook fixes, and packaged-build dependency corrections round out the release.
VS Code now spawns the bundled nexql-mcp binary directly. Ephemeral profiles emit TLS settings for Neon, Supabase and RDS; SSH-tunnelled connections are named rather than failing opaquely.
FAQ
No. NexQL Free AI autoloads as the default provider — no key, no account, no configuration. If you would rather use your own, OpenAI, Anthropic, Gemini, GitHub Models, VS Code LM, Ollama, LM Studio and custom endpoints are all supported, each with its key stored separately in the OS keychain.
No. The execution model is notebook-first: the assistant writes SQL into a cell and stops. You review it and press run. Risky statements against a Production-tagged connection require an extra confirmation on top of that.
The core is MIT and builds a fully working free extension you may fork, rebrand and publish under your own ID. The Marketplace build adds proprietary premium features on top of that core.
Yes — anything speaking the PostgreSQL wire protocol. Use the direct (non-pooler) endpoint on Neon, and direct or the session pooler on port 5432 for Supabase; transaction-mode poolers break cross-cell transactions, LISTEN/NOTIFY and temp tables.
Through VS Code SecretStorage, which is encrypted by the OS keychain — Keychain on macOS, Credential Manager on Windows, libsecret on Linux. Nothing is written in plain text, and .pgpass files are supported.
No SQL text, schema or object names, hostnames, database names, usernames or credentials. Payloads are allowlisted and bucketed, VS Code global telemetry is a hard gate, and the mode can be set to off.
Install, add a connection, open a notebook. That is the whole setup.
# VS Code: Ctrl+P, then paste
ext install ric-v.postgres-explorerAlso on Open VSX. Pair it withNexQL themes.