<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgres on Vibe Coding</title><link>https://vibecoding.rest/tags/postgres/</link><description>Recent content in Postgres on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/postgres/index.xml" rel="self" type="application/rss+xml"/><item><title>Supabase</title><link>https://vibecoding.rest/mcp-servers/supabase/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/supabase/</guid><description>&lt;p&gt;Supabase&amp;rsquo;s official MCP server gives an agent access to a Supabase project&amp;rsquo;s Postgres schema and data, Edge Functions, and project configuration, with a read-only mode for safer exploratory use. It&amp;rsquo;s built and maintained directly by the Supabase team.&lt;/p&gt;</description></item><item><title>Postgres Query Skill</title><link>https://vibecoding.rest/skills/postgres-query-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/postgres-query-skill/</guid><description>&lt;p&gt;This skill executes safe, read-only SQL queries against PostgreSQL databases, with multi-connection support and defense-in-depth safeguards against destructive statements.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Letting a model run arbitrary SQL against a real database is risky without hard guardrails. Restricting the skill to read-only queries with explicit safeguards makes database exploration usable without risking accidental writes.&lt;/p&gt;</description></item></channel></rss>