4 ms·
Show HN: Pglens – 27 read-only PostgreSQL tools for AI agents via MCP
- jeeybee 6mo agoMost Postgres MCP servers expose query and list_tables. Agents end up guessing column values, enum casing, and join paths - then retrying until something works. pglens gives agents the context to get it right the first time: column_values shows real distinct values with counts, find_join_path does BFS over the FK graph and returns join conditions through intermediate tables, describe_table gives columns/PKs/FKs/indexes in one call. Plus production health tools like bloat_stats, blocking_locks, and sequence_health. Everything runs in readonly transactions, identifiers escaped via Postgres's quote_ident(), no extensions required. Works on any Postgres 12+ (self-hosted, RDS, Aurora, etc.). Two dependencies: asyncpg and mcp. https://github.com/janbjorge/pglens https://github.com/janbjorge/pglens pip install pglen
- agent_anuj 6mo ago[dead]
- nadav_tal 6mo ago[flagged]
- ForHackernews 6mo agoI don't know why but all your comments are getting hidden/flagged/killed for some reason.
- nadav_tal 6mo ago[flagged]
- jeeybee 6mo ago[dead]
- Copperline-Labs 6mo ago[flagged]
- edinetdb 6mo ago[flagged]
- petervandijck 6mo agoThis is really nicely, read only is the right way to start
- jeeybee 6mo agoThanks! Read-only felt like the obvious constraint; agents shouldn't need write access to understand a database.
- saltpath 6mo agoRead-only by design is a smart constraint for agent tooling — eliminates a whole class of "oops the LLM dropped my table" failure modes. Curious about a couple things: how do you handle schema introspection? Do the tools auto-discover tables/columns or is there a config step? And for the query tools, is there any cost/complexity guardrail (e.g. preventing a full sequential scan on a 500M row table)?
- jeeybee 6mo agoNo config step, the tools discover everything from pg_catalog at call time. list_schemas → list_tables → describe_table is the typical agent workflow, and there's a query_guide prompt baked in that suggests that progression. On query guardrails: every query runs in a readonly transaction and results are capped at 500 rows via a wrapping SELECT * FROM (...) sub LIMIT 500. There's also explain_query which returns the plan without executing, so agents can check before running something expensive. That said, there's no cost-based gate that blocks a bad plan automatically; that's an interesting idea worth exploring.
- kiyeonjeon 6mo agoThe column_values tool solves a surprisingly annoying problem. Agents confidently writing WHERE status = 'active' when the real value is 'ACTIVE' or 'enabled' causes a lot of unnecessary back-and-forth. Nice that it's addressed explicitly.