NexQL Postgres MCP

Name: NexQL Postgres MCP
Author: NexQL-OSS

by NexQL-OSSversion 0.2.4i★ –iRuns on your computer

Registry nameio.github.NexQL-OSS/nexql-mcp

Install

Overview

Description from the maker (original English)

Standalone Postgres MCP server — schema-aware, read-only by default, installable everywhere.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 366/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Databases & datasets
You need to fill in: DATABASE_URL

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: DATABASE_URL, NEXQL_MCP_CONFIG

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "nexql": {
      "command": "npx",
      "args": [
        "-y",
        "nexql-mcp"
      ],
      "env": {
        "DATABASE_URL": "your-value",
        "NEXQL_MCP_CONFIG": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add nexql --env DATABASE_URL=your-value --env NEXQL_MCP_CONFIG=your-value -- npx -y nexql-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nexql": {
      "command": "npx",
      "args": [
        "-y",
        "nexql-mcp"
      ],
      "env": {
        "DATABASE_URL": "your-value",
        "NEXQL_MCP_CONFIG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nexql": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "nexql-mcp"
      ],
      "env": {
        "DATABASE_URL": "your-value",
        "NEXQL_MCP_CONFIG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

DATABASE_URL secret env
Postgres connection string, used when no positional URL or --profile is given.
NEXQL_MCP_CONFIG env
Path to config.toml (default: ~/.config/nexql-mcp/config.toml).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account NexQL-OSS, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Databases & datasetsi

More stars than 0% of the other 1151 servers in this category
Published to the registry more recently than 21% of the other 1151 servers in this category
Basic checks equal to or better than 100% of the other 1151 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is NexQL Postgres MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: DATABASE_URL

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.4) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Rust on your computer.

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

by supabaseWidely used↓ 235.4K/wk★ 3KUpdated 2 days ago

Computer or cloud✓ supabase.com

Install

MongoDB MCP Server

MongoDB Model Context Protocol Server

by mongodb-jsWidely used↓ 157.1K/wk★ 1.2KUpdated 4 days ago

Runs on your computer

Install

Elasticsearch MCP Server

MCP server for interacting with Elasticsearch

by cr7258Growing↓ 2.7K/wk★ 315Updated 14 months ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

nexql-mcp

Standalone Postgres MCP server — schema-aware, read-only by default, installable everywhere.

NexQL Pro ships an in-process MCP server locked to VS Code (pro/src/mcp/). This repo extracts that capability into an independent Rust binary any MCP client can spawn: Claude Desktop, Cursor, VS Code Copilot, Zed, etc.

Status: Phases 0–6 + Phase 7 extension cutover (stdio spawn) + Phase 8 HTTP (bearer, sessions, rate limit) + Phase 9 write/admin tools landed. 55 tools across Schema, Query, Context, Perf, Write, and Admin. Full OAuth gateway stays pro-only; session-store LRU eviction cap not yet implemented. See docs/CUTOVER.md.

Why this exists

Competing Postgres MCP servers expose connect → run query → return rows. Models hallucinate table names against schemas that do not exist. NexQL's moat is the offline schema index (TF-IDF, join graph with inferred FKs, value profiles, optional embeddings, RRF fusion) built in pro/src/features/dbindex/. This repo ports that index plus 54 query/schema/DBA/meta tools from Pro into a fast, trivially installable binary.

Architecture

crates/

├── nexql-mcp/ CLI, subcommands, wiring (binary) ├── nexql-proto/ MCP JSON-RPC types, transports ├── nexql-tools/ tool registry, schemas, executors ├── nexql-index/ dbindex port (builder, store, lexical, joins, embed) ├── nexql-conn/ connection resolution, pool, credentials └── nexql-policy/ access modes, allow/deny, PII, caps, audit npm/ npx shim (per-platform optionalDependencies) mcpb/ one-click Claude Desktop bundle docs/ per-client setup, tool reference

Layering is one-directional: policy + conn are leaves → index → tools → binary. nexql-tools never depends on nexql-proto.

Scope boundary: nexql-mcp manages objects *within* a connected database (tables, indexes, columns, …), not the database catalog itself. CREATE DATABASE / DROP DATABASE are rejected in every access mode — permanent, intentional scope, not a gap. See docs/tools/README.md and docs/REFERENCE.md.

Install

Claude Desktop — one download

Get the bundle for your computer from [nexql-mcp.astrx.dev/install](https://nexql-mcp.astrx.dev/install), double-click it, and paste your database URL. No terminal, Node or PATH setup. The install form also has an "Allow changes to data" switch (off by default) and an optional schema list.

npx — recommended for every other client

npx -y nexql-mcp@latest postgres://dev@localhost:5432/appdb doctor

-y skips the "ok to proceed?" confirmation prompt; @latest always resolves the newest published release instead of whatever npx happens to have cached — always use both together. This is the desired way to run nexql-mcp: no separate install step, nothing added to PATH, works identically whether a human is typing it or an AI agent is running it on your behalf. Requires Node.js (npx ships with it) — nothing else.

# Verify

npx -y nexql-mcp@latest --version

Setup

npx -y nexql-mcp@latest setup # initialize connections and db profiles

Wire your MCP client (or run the guided wizard)

npx -y nexql-mcp@latest init cursor # Cursor npx -y nexql-mcp@latest init claude-desktop # Claude Desktop npx -y nexql-mcp@latest init vscode-copilot # VS Code Copilot npx -y nexql-mcp@latest tui # interactive profile + client wiring

Client config (command/args) uses the same pattern — no install step for the client to rely on either:

"mcpServers": { "nexql-mcp": { "command": "npx", "args": ["-y", "nexql-mcp@latest", "--profile", "mydb"] } } }

If you are an AI coding agent setting this up on a user's behalf: run npx -y nexql-mcp@latest init --apply — non-interactive, no browser needed, writes the merged client config directly (.mcp.json for claude-code, claude_desktop_config.json for claude-desktop, etc. — see docs/clients/README.md for exact paths per client). Or drive nexql-mcp setup's HTTP API directly: POST /api/v1/clients/preview → POST /api/v1/clients/apply (bearer token printed to stderr on startup). Prefer this over hand-writing claude mcp add-style shell commands or hand-parsing/merging the client's JSON config yourself.

Per-client config paths and paste blocks: docs/clients/README.md.

npm install -g nexql-mcp also works if you'd rather have a permanent nexql-mcp on PATH than repeat npx -y nexql-mcp@latest — same shim, same @nexql/mcp- - prebuilt binaries, no Rust toolchain needed either way.

Linux system requirements: prebuilt GNU/Linux binaries target glibc 2.35+ (Ubuntu 22.04, Debian 12, RHEL 9, and newer). If npx/npm fails with GLIBC_2.39 not found, use one of the fallback methods below (cargo install builds from source; Docker sidesteps glibc entirely). Musl/static Linux builds are not published yet.

Other install methods (fallback)

Reach for one of these only if npx isn't an option — an offline/air-gapped environment, a CI image that wants a pinned binary baked in, no Node.js available, or you simply prefer a permanent install. All ship the same binary as the npm package.

Quick install script (Linux / macOS / Windows) — installs a permanent binary, no Node.js required

Linux & macOS — downloads the latest release, installs to /usr/local/bin (or ~/.local/bin if sudo is unavailable), then prints setup steps:

curl -fsSL https://raw.githubusercontent.com/NexQL-OSS/mcp/main/scripts/install.sh | bash

Pin a version:

curl -fsSL https://raw.githubusercontent.com/NexQL-OSS/mcp/main/scripts/install.sh | NEXQL_MCP_VERSION=v0.2.2 bash

Windows (PowerShell) — installs to %LOCALAPPDATA%\Programs\nexql-mcp and adds it to your user PATH:

irm https://raw.githubusercontent.com/NexQL-OSS/mcp/main/scripts/install.ps1 | iex

Pin a version:

$env:NEXQL_MCP_VERSION = "v0.2.2"; irm https://raw.githubusercontent.com/NexQL-OSS/mcp/main/scripts/install.ps1 | iex

Or download and run the scripts locally: scripts/install.sh · scripts/install.ps1. Once installed, drop the npx -y nexql-mcp@latest prefix and call nexql-mcp directly for every command above.

uv (PyPI)

uv installs CLI tools from PyPI into isolated environments — same prebuilt binary, no Rust toolchain.

Install uv itself (if needed):

curl -LsSf https://astral.sh/uv/install.sh | sh   # macOS / Linux

irm https://astral.sh/uv/install.ps1 | iex        # Windows

Install nexql-mcp:

uv tool install nexql-mcp

uv tool update-shell # once, if uv warns the tool bin dir is not on PATH

One-off without installing (uv's equivalent of npx -y):

uvx nexql-mcp postgres://dev@localhost:5432/appdb doctor

Pin a version:

uv tool install 'nexql-mcp==0.2.2'

Upgrade later:

uv tool upgrade nexql-mcp

PyPI status: wheels are not published yet. Until the first PyPI release lands, use npx or the quick install script above. Maintainer steps: docs/publish-pypi-uv.md.

cargo (crates.io) — builds from source

cargo install nexql-mcp

Needs clang/libclang first (pg_query's bindgen requires it):

sudo apt install clang libclang-dev   # Debian/Ubuntu

sudo pacman -S clang # Arch

Manual download — grab a release archive by hand

From the Releases page:

Platform	Archive
Linux x64	`nexql-mcp- -x86_64-unknown-linux-gnu.tar.gz`
Linux arm64	`nexql-mcp- -aarch64-unknown-linux-gnu.tar.gz`
macOS Intel	`nexql-mcp- -x86_64-apple-darwin.tar.gz`
macOS Apple Silicon	`nexql-mcp- -aarch64-apple-darwin.tar.gz`
Windows x64	`nexql-mcp- -x86_64-pc-windows-msvc.tar.gz`

Extract and put nexql-mcp (or nexql-mcp.exe) on your PATH.

Docker

Prebuilt, published on every release to GHCR:

docker run --rm -i ghcr.io/nexql-oss/mcp:v0.6.0 postgres://dev@host.docker.internal:5432/appdb

or: ghcr.io/nexql-oss/mcp:latest

Or build locally from the distroless Dockerfile:

docker build -t nexql-mcp:0.6.0 .

docker run --rm -i nexql-mcp:0.6.0 postgres://dev@host.docker.internal:5432/appdb

Claude Desktop (MCPB one-click bundle)

Each release attaches a platform .mcpb bundle (nexql-mcp- .mcpb). nexql-mcp.astrx.dev/install picks the right one for your OS; they are also on the Releases page. Double-click to install into Claude Desktop. The install form maps to DATABASE_URL, NEXQL_MCP_ALLOW_WRITES and NEXQL_MCP_SCHEMAS. Built from mcpb/manifest.json via scripts/package-mcpb.sh.

Homebrew

No published tap yet — each release renders a formula (Formula/nexql-mcp.rb, via scripts/render-homebrew-formula.sh) and attaches it as a release asset for a future homebrew-tap repo to pick up. Until that tap exists, use npx or the quick install script above.

MCP Registry

Listed in the official MCP Registry as io.github.NexQL-OSS/nexql-mcp (server.json), published automatically after each release via GitHub OIDC (no stored credentials) — see .github/workflows/publish-mcp-registry.yml.

mcp-name: io.github.NexQL-OSS/nexql-mcp

From source

export LIBCLANG_PATH="${LIBCLANG_PATH:-/usr/lib}"   # or your llvm lib dir

cargo build --release -p nexql-mcp ./target/release/nexql-mcp postgres://dev@localhost:5432/appdb

Updates

Once a day nexql-mcp asks the npm registry (registry.npmjs.org/nexql-mcp/latest) for the newest version. The request sends nothing about you or your database, only a nexql-mcp/ user agent. When a newer release is out, the chat gets a short notice with the upgrade command for the way you installed it: npx, npm, pnpm, bun, Volta, cargo, uv, pipx, pip, Homebrew, Docker, the install script or the Claude Desktop bundle. The model passes it on and, if it can run commands on your machine, offers to run it for you. nexql-mcp doctor prints the same line.

npx configs need nexql-mcp@latest. With no tag, npx -y nexql-mcp keeps running the copy npx cached first.

Turn the check off with --no-update-check, NEXQL_MCP_NO_UPDATE_CHECK=1, update_check = false in config.toml, or DO_NOT_TRACK=1. It is also off when CI is set, and fails quietly offline.

Set up a connection

Commands below assume nexql-mcp resolves on PATH. If you're running via npx instead, prefix each one with npx -y nexql-mcp@latest in place of nexql-mcp — see Install.

One-off, no config — pass a connection string directly:

nexql-mcp postgres://dev@localhost:5432/appdb

Saved profiles — put connections in `~/.config/nexql-m

Only the beginning is shown; read the rest in the repo

NexQL Postgres MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Databases & datasetsi

Common questions

Alternatives

Supabase

MongoDB MCP Server

Elasticsearch MCP Server

README from the maker

nexql-mcp

Why this exists

Architecture

Install

Claude Desktop — one download

npx — recommended for every other client

Setup

Wire your MCP client (or run the guided wizard)

Other install methods (fallback)

or: ghcr.io/nexql-oss/mcp:latest

Updates

Set up a connection