postgres

Our take

One of a dozen-plus registry entries WayStation publishes against a single repo: each points at a per-app remote endpoint (here waystation.ai/postgres/mcp) of their hosted no-code integration hub, and a PostgreSQL connector does exist on their marketplace. The repo itself contains no Postgres code at all — it is the deprecated local stdio proxy (a single ~200-line index.ts that reads a token file and forwards to their API) plus a marketing README, untouched since September 2025, with the npm shim at ~5 downloads/week. Everything real happens server-side: you create a WayStation account, connect Postgres through their dashboard, and hand your database credentials and query traffic to their hosted service over streamable HTTP/SSE with per-user preauthenticated URLs. No published tool list or schema for the Postgres connector is verifiable from the repo, and there is no self-hosting path. For users who explicitly want a managed, no-code hub and accept a third party in their database path; anyone wanting an auditable Postgres MCP server should use a local one instead.

reviewed by hand · 2026-07-05

Something wrong or dead here? Report it

Verification record

last verified

yesterday

github stars

57

last commit

10 mo ago

archived

no

in registry since

2025-09-09

github.com/waystation-ai/mcp