YawLabs Postgres MCP
YawLabs Postgres MCP is an MCP server published by YawLabs; its MCP spec-revision support has not been verified yet. It is a community implementation. Last verified 2026-08-27.
Does YawLabs Postgres MCP support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision YawLabs Postgres MCP supports (as of 2026-08-27).
Is YawLabs Postgres MCP a first-party (official) MCP server?
No. YawLabs Postgres MCP is a community-published MCP server from YawLabs, not a first-party vendor server (last verified 2026-08-27).
How do I connect to YawLabs Postgres MCP?
YawLabs Postgres MCP is available via the package npm:@yawlabs/postgres-mcp, the official MCP Registry under io.github.YawLabs/postgres-mcp, the source repository at https://github.com/YawLabs/postgres-mcp. Authentication: unknown. Transports: stdio.
When were YawLabs Postgres MCP's facts last verified?
2026-08-27. Each fact on this page links to the sources used to verify it.
A PostgreSQL MCP server from YawLabs covering queries, schema introspection, EXPLAIN plans, and health checks. It starts read-only: writes work only when explicitly enabled through an environment variable, so an agent cannot silently modify a database it was pointed at. Ranked #102 in the MCP 500 at the 2026-08-14 snapshot.
Spec revision support has not been verified for this entry.
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.YawLabs/postgres-mcp at version 0.12.0 (active, updated 2026-08-23) - lists package npm:@yawlabs/postgres-mcp - accessed
- YawLabs/postgres-mcp README - "Query a PostgreSQL database from Claude Code, Cursor, and any MCP client. Read-only by default - writes opt in via a single env var"; built and maintained by Yaw Labs (yaw.sh); MIT license, pushed 2026-08-23 - accessed
- npm package @yawlabs/postgres-mcp - latest 0.12.0 (2026-08-23), maintainer jeffyaw - accessed