SQLX runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Oct 2026.
Run SQL on 30+ databases through saved, encrypted connections; credentials stay local.
What the code does
We read the source, 5 d ago · rules 995398eba69f
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(binary, args, {
const candidate = path.join(stage, entrypoint);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to SQLX
same job, measured the same wayQuery and explore 100+ databases through your DBCode connections.
PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials.
AI access to Quadratic spreadsheets: open files, run Python/SQL, query connected databases.
Run SQL queries and inspect database schemas through safe, visible MCP tools.
Query databases from AI agents using connections configured in DBX.
MCP server for SQLCipher 4 encrypted SQLite databases with full CRUD operations and query support
MCP server for local SQLite database operations
Query any database in plain English or SQL through a guardrailed, read-only data layer.
SQLX — questions
Answers built from our own checks of this server.