Postgres MCP vs QueryWeaver
A side-by-side look at the Postgres MCP and QueryWeaver MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Postgres MCP for databases work as a local process; choose QueryWeaver for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Postgres MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DATABASE_URI.
Choose QueryWeaver when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 56/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | DATABASE_URI | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,420 | 1,086 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Postgres MCP | View QueryWeaver |
Tools & capabilities
Postgres MCP tools
No tool names declared yet. Check the project README from the listing page.
QueryWeaver tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
Postgres MCP
{
"mcpServers": {
"crystaldba-postgres-mcp": {
"command": "uvx",
"args": [
"postgres-mcp"
],
"env": {
"DATABASE_URI": "YOUR_DATABASE_URI_HERE"
}
}
}
}
QueryWeaver
{
"mcpServers": {
"queryweaver": {
"command": "uvx",
"args": [
"queryweaver"
]
}
}
}
Frequently asked questions
Postgres MCP is categorized under Databases and uses a local stdio subprocess. QueryWeaver belongs to Databases and uses a local stdio subprocess. Pick Postgres MCP for databases work and QueryWeaver for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Postgres MCP is listed as free. Auth: api key required. QueryWeaver has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add crystaldba-postgres-mcp and queryweaver as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Postgres MCP has a quality signal of 56/100 (Good) with 4 views, 0 installs and 3,420 GitHub stars. QueryWeaver has 48/100 (Fair) with 3 views, 0 installs and 1,086 GitHub stars.