NexQL Postgres MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 50 installs a week from npm. Last commit 31 Oct 2026.
Standalone Postgres MCP server — schema-aware, read-only by default, installable everywhere.
We read the source, 1 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
const result = spawnSync(binaryPath, process.argv.slice(2), {
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const result = spawnSync(binaryPath, process.argv.slice(2), {
const candidate = path.join(pkgRoot, subpath);
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
if exists(Path::new("/.dockerenv")) {
SELECT blks_hit, blks_read, CASE WHEN blks_hit + blks_read = 0 THEN NULL
el.innerHTML = notice(kind, html);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch NexQL Postgres MCP and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add nexql-mcp -- npx -y nexql-mcp
{
"mcpServers": {
"nexql-mcp": {
"command": "npx",
"args": [
"-y",
"nexql-mcp"
]
}
}
}
[mcp_servers.nexql-mcp]
command = "npx"
args = ["-y", "nexql-mcp"]
{
"mcpServers": {
"nexql-mcp": {
"command": "npx",
"args": [
"-y",
"nexql-mcp"
]
}
}
}
{
"servers": {
"nexql-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nexql-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
DATABASE_URL (Postgres connection string, used when no positional URL or --profile is given), NEXQL_MCP_CONFIG (Path to config.toml (default: ~/.config/nexql-mcp/config.toml)).
MCP server for PostgreSQL. Read-only by default, row caps, timeouts, secrets never logged.
Production-grade PostgreSQL MCP server — 254 tools for query, tuning & ops, read-only by default.
Text-to-SQL MCP server: read-only queries on PostgreSQL, MySQL and SQL Server with your real schema
Read-only Postgres: drop-in for the archived server-postgres, with schema context.
MCP server for SAP SQL Anywhere 17: explore schemas and run read-only queries.
Read-only SQL, plans, schema for AI agents: PostgreSQL, Oracle, SQL Server, Firebird, SQLite, JDBC
PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.
MCP server for MySQL. Read-only by default, row caps, statement timeouts, secrets never logged.
Answers built from our own checks of this server.