pgEdge Postgres MCP — Read-Only by Default + Web UI

Practical Notes

• Quant: the docs show a YAML config format and multiple transports (stdio/HTTP), so you can standardize across local and shared deployments.
• Quant: treat read-only as the default baseline; enable writes only with a config change (allow_writes) and a human approval rule.

Rollout pattern

• Start in stdio mode from a developer laptop, validate core tools, then graduate to HTTP mode for shared access.
• Create a dedicated DB user and keep permissions minimal; rely on the server’s explicit write-enable switch.
• Add audit logging and a trace file before you let multiple teammates point agents at the same server.

Watchouts

If you enable HTTP mode for shared use, treat it like a real service: auth on, TLS when possible, and least-privilege DB credentials.

FAQ

Q: Do I need the web UI? A: No. You can run it purely as an MCP server over stdio for local development and keep the surface area small.

Q: How do writes work? A: The server is read-only by default. Writes require explicitly enabling them via configuration (for example allow_writes).

Q: What is the simplest first test? A: Run SELECT 1 via the query tool, then inspect one table schema to confirm connectivity and metadata access.