Codex isn't able to execute queries because authentication fails

[adossey]

I have several working connections in DBeaver, but Codex isn't able to execute any queries in any of the connections. Here's the output from Codex:

Tried running select now(); against [Conenction name 1] and [Connection name 2], but both connections rejected the request because the saved credentials aren’t valid (Postgres reports “password authentication failed” and the production host also requires SSL). Once the stored passwords (and SSL settings if needed) are updated in DBeaver, I can rerun the query. Suggested next step: 1) Update the connection credentials/SSL configuration in DBeaver and let me know when to try again.

Unfortunately, these connection are already properly configured in DBeaver. This is version 1.1.7 manually installed, but I also tried 1.1.3 installed via npm.

[srthkdev]

Fixed in v1.2.3

• Uses DBeaver’s stored credentials (decrypted from credentials-config.json) instead of prompting/guessing.
• Maps SSL settings from DBeaver (sslmode, sslrootcert, sslcert, sslkey) to the Postgres client.
• No longer depends on the psql binary; a native Postgres client (pg) is used.
• Clean MCP stdout (logs moved to stderr) so tools show correctly in clients like Cursor.

Upgrade

npm uninstall -g dbeaver-mcp-server
npm install -g dbeaver-mcp-server@latest
dbeaver-mcp-server --version   # should show 1.2.3

Cursor MCP config

Update ~/.cursor/mcp.json:

{
  "mcpServers": {
    "dbeaver": {
      "command": "dbeaver-mcp-server",
      "env": {
        "DBEAVER_TIMEOUT": "120000",
        "DBEAVER_DEBUG": "true"
      }
    }
  }
}

Then restart Cursor.

Test

• “List my database connections”
• “Run SELECT now() on [your connection name]”

Notes on credentials and SSL

• The server reads the exact credentials DBeaver saves in credentials-config.json (decrypted internally), so it uses the same username/password you use in DBeaver.
• SSL is honored from DBeaver driver properties:
  • sslmode/ssl.mode/ssl (supports: disable, require, verify-ca, verify-full)
  • sslrootcert, sslcert, sslkey (file paths)
• If cert files are set in DBeaver, ensure the files are readable by the MCP server process.

If you still see auth errors

• “role 'postgres' does not exist”: Your connection is saved with user “postgres”, but that role isn’t present on the server. Update the username in DBeaver (check “Save password”), reconnect once in DBeaver to refresh the store, then retry.
• “password authentication failed”: Re-save the password in DBeaver (tick “Save password”), reconnect once in DBeaver, then retry.
• Tools show red in Cursor: confirm dbeaver-mcp-server --version => 1.2.3, and restart Cursor. If needed, share the last lines of the Cursor log “MCP user-dbeaver.log” (Cursor > logs folder) to diagnose further.

This should let them run successfully on the latest version and gives clear next steps if anything still fails.