Supabase MCP

The Supabase MCP server exposes Postgres tables and pgvector similarity search directly to an agent, so a model can query your application database — and your embeddings — as a native capability rather than through a hand-built tool.

What it unlocks

• Structured lookups. "How many active accounts signed up last week" resolves against the real schema.
• Vector search. With pgvector exposed, an agent can do semantic retrieval over your own content without a separate vector store.

That combination makes it a compact backbone for retrieval-augmented workflows on data you already hold in Supabase.

The caveat

Direct database access from a model is powerful and needs scoping. Use a role with only the permissions the task requires, keep row-level security enforced, and gate any write path behind human review.

Who should use it

Teams already on Supabase who want agents to read application data and do semantic search over their own content. If your data lives elsewhere, a database-specific connector is the better fit.