integration-postgres

To connect a PostgreSQL database to an AI agent over SSH, you need to store and verify the connection string on your VPS. This process registers the database for stdio-based access and performs a live connection smoke test to confirm the integration.

MCP integration for PostgreSQL registers a postgres-mcp server for stdio-based access, allowing an AI agent to interact with your database. It works by securely storing the connection string on the VPS and reloading the gateway to enable live agent database queries.

You do not strictly need a read-only user to connect PostgreSQL to a self-hosted Hermes agent, but it is strongly encouraged. The setup applies safety guardrails that reject risky superuser credentials by default and support both read-only and read-write setups.

Yes, you can use psql or psycopg2 as fallback support for PostgreSQL MCP server registration. These optional dependencies help facilitate idempotent rollout and rollback-safe wiring when connecting your database to the Hermes VPS.

The limitation of using superuser credentials for PostgreSQL database onboarding is that the system rejects them by default for safety. The setup enforces scoped read-only users to prevent risky operations, though read-write setups are also supported with proper guardrails.

To verify a live PostgreSQL connection after gateway reloads, the system performs operational smoke tests. These tests confirm the integration works by checking the active connection status on the VPS after the Hermes gateway has been successfully reloaded.