query
Run a read-only SQL query
LABSCO SUMMARY
Read-only is the tool's own contract, not something the prompt has to keep reminding the model about.
There is one tool and it runs read-only SQL, so nothing an agent composes can write, and a badly formed statement costs a failed query rather than a changed row. Which schemas are visible belongs to the server rather than to the query, which means the boundary of what can be seen is decided once, by whoever started it.
What it is
A single-tool PostgreSQL bridge that executes read-only SQL over the schemas the server was started against.
What you get
- query, which runs a read-only SQL statement and returns the result.
- More than one schema visible to the same statement, so a join across them is one call.
Requirements
Nothing to supply — no account, no key. A reachable PostgreSQL database and the list of schemas to expose, both settled when the server starts rather than per call.
Setup effort
One command — npx -y mcp-server-postgres-multi-schema <YOUR_DATABASE_URL> [schemas]
USE CASES
01
Answering a question that spans more than one schema
Both schemas are already in scope, so a join across them is written as ordinary SQL and executed read-only in one call.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"postgres": {
"command": "npx",
"args": [
"-y",
"mcp-server-postgres-multi-schema",
"postgresql://localhost/mydb",
"public,audit"
]
}
}
}npx
TERMINAL
npx -y mcp-server-postgres-multi-schema <YOUR_DATABASE_URL> [schemas]
