A side-by-side look at the Postgres and Zektor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Postgres for databases work as a local process; choose Zektor for databases. You can also run both side by side in one mcpServers block.
DATABASE_URL.query, schema, table_info.Rows where the two servers differ are marked.
queryExecute SQL (SELECT, WITH, EXPLAIN, SHOW, ANALYZE). Returns a text table.schemaTables in a schema (default `public`) with columns and approximate row countstable_infoOne table: columns, types, null/default, PK, exact row countexplainEXPLAIN (FORMAT TEXT), optional ANALYZElist_schemasList non-system schemasNo tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"postgres": {
"command": "npx",
"args": [
"-y",
"mcp-pg-server"
],
"env": {
"DATABASE_URL": "YOUR_DATABASE_URL_HERE"
}
}
}
}
No confirmed install command for Zektor yet — follow the setup steps linked from its listing page rather than a guessed package name.
| GitHub stars | 0 | 1 |
|---|
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
|---|
| Tools | 5 | Not listed |
|---|
| Full listing | View Postgres | View Zektor |
|---|