> ## Documentation Index
> Fetch the complete documentation index at: https://012e27a-docs-2.manicule.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://012e27a-docs-2.manicule.dev/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://012e27a-docs-2.manicule.dev/api/mcp.
> Every agent surface: https://012e27a-docs-2.manicule.dev/.well-known/llms-manifest.json

# Supabase Connector (/connectors/supabase)

<!-- agent-signals: reading_time_min: 1 · est_tokens: 266 · updated: 2026-11-12 -->
Related: [Connectors & Integrations](/connectors/overview.md), [GitHub Connector](/connectors/github.md), [GitLab Connector](/connectors/gitlab.md), [Vercel Connector](/connectors/vercel.md), [Netlify Connector](/connectors/netlify.md), [Neon Postgres Connector](/connectors/neon.md)

> Managed Postgres, auth, storage, and edge functions wired into your project.

The **Supabase connector** links a project to Supabase's backend: PostgreSQL, Auth, Storage,
and Row Level Security.

## Capabilities

* **1-click provisioning**: create and link a Supabase project from Cloud Studio.
* **Credential binding**: sets `SUPABASE_URL`, `SUPABASE_ANON_KEY`, and `DATABASE_URL` in your
  environment.
* **Client setup**: installs `@supabase/supabase-js` and creates the client with typed tables.

## Setup

<Steps>
<Step title="Connect Supabase">Go to **Connectors** and click **Connect** on **Supabase**.</Step>

<Step title="Authorize">Approve the integration on Supabase and select your organisation.</Step>

<Step title="Provision">In Cloud Studio, open the **Databases** drawer, pick **Supabase**, and click
**Provision database**.</Step>
</Steps>

<Warning title="Keep the service key server-side">Only the anon key belongs in client code. Service-role keys bypass Row Level Security, so
keep them in server routes or environment variables.</Warning>