PgDog MCP (built-in, Enterprise)
access level: read-onlyโ Source-reviewed Oct 2026
We read this project's source code and tool definitions (Oct 2026). This is a code review, not a live test against real systems. Re-check after upgrades.
| Repository | https://pgdog.dev/blog/mcp |
|---|---|
| Category | Observability |
| Systems touched | PgDog PostgreSQL proxy/pooler on Kubernetes: running instances, real-time per-database metrics, container logs, applied config |
| Access (as described) | read-only |
| License / price | PgDog Enterprise (paid); PgDog core AGPL-3.0 |
| GitHub stars | 5614 |
| Read tools | proxy_instances, proxy_metrics, proxy_logs, proxy_config |
| Write / delete / exec tools | None (vendor states agents cannot change settings or deployment config) |
| Read-only mode | N/A (read-only by design) |
| Safety notes | Token auth on the control plane โ treat the MCP token like a database-ops credential, since logs and config can reveal hostnames, users and query details. Paid Enterprise feature; not available in the open-source build. |
| Verified | yes (vendor announcement review 2026-11-14; not source-reviewed โ Enterprise feature) |
| Notes | Built-in MCP on the PgDog Enterprise control plane /mcp endpoint, shipped in release v2026-11-12; enabled via Helm values (control.config.mcp.enabled). Stars are for the open-source pgdogdev/pgdog repo. Added 2026-11-14. |
๐ฌ SysAdmin Agents
The SysAdmin Agents newsletter: new MCP servers, agent skills and safety notes for sysadmins. One email a week.