Postgresql Connection

PostgreSQL Connection Skill

On Entry

Tell the user:

Setting up PostgreSQL connection — I'll configure and test a connection to your source PostgreSQL database. I'll need a few connection details.

Prerequisites

• Network access to the PostgreSQL host (managed: RDS / Cloud SQL / Azure / Supabase / Neon, or self-hosted)
• PostgreSQL username and password
• The scai CLI installed and available

Required Connection Details

Standard Auth (only auth method supported in MVP)

SSL defaults to Require so managed PG (RDS, Cloud SQL, Azure, Supabase, Neon) works out of the box. For local Docker / dev, override with --ssl-mode Disable explicitly.

Workflow

Step 1: Ask How to Provide Credentials

Ask the user:

"I need the following to connect to PostgreSQL:

• Host
• Port (default 5432)
• Database name
• Username and password
• SSL mode (default Require is right for managed PG)

How would you like to provide these?"

Options:

1. 1Password — Credentials stored in 1Password vault
2. Enter manually — Provide values directly

Step 2: Route Based on Answer

Step 3: Add the Connection

scai connection add-postgresql \
  -c <CONNECTION_NAME> \
  --auth standard \
  --host <HOST> \
  --port <PORT> \
  --database <DATABASE> \
  --user <USERNAME> \
  --password <PASSWORD> \
  --ssl-mode Require

• Omit --port if the server uses the default (5432).
• For local Docker / unencrypted dev databases, use --ssl-mode Disable:

scai connection add-postgresql \
  -c <CONNECTION_NAME> \
  --auth standard \
  --host localhost \
  --port 5432 \
  --database <DATABASE> \
  --user <USERNAME> \
  --password <PASSWORD> \
  --ssl-mode Disable

Step 4: Save and Test Source Connection

Call the configure tool with source_connection set to <CONNECTION_NAME>. The MCP server runs scai connection test internally and only persists the connection if the test passes.

• On success: the response includes connection_test: ok.
• On failure: the tool returns an error containing the scai message. Surface it to the user, help them fix the issue, then re-run configure(source_connection=<CONNECTION_NAME>).

Common errors:

CHECKPOINT

Confirm with user:

• configure returned connection_test: ok
• Connection appears in scai connection list -l postgresql --json
• Source connection saved to session config

On Completion

After the CHECKPOINT passes, tell the user:

Connection configured — Successfully connected to PostgreSQL using connection <connection_name>.

Then return to the calling skill.

Security Rules

• NEVER log or display secrets (passwords) in plain text.
• NEVER include secrets in command-line arguments that might be logged. Prefer a credential manager (e.g. 1Password op run, or use /secrets capability from Cortex Code to store them).
• For managed PG, keep --ssl-mode Require (or stricter). Only relax for trusted local dev.

Quick Reference