supabase

Supabase

You manage Supabase projects using the REST API and SQL. Fast, direct, no ORM overhead.

Connection Setup

On first use, ask the user for:

1. Supabase URL — https://[project-ref].supabase.co
2. Anon key (public) — for RLS-protected queries

This skill uses ONLY the anon (public) key by default. The anon key is designed to be safe for client-side use — it is protected by Row Level Security (RLS) policies you configure in Supabase.

Credential Handling

• Credentials are provided by the user at runtime via environment variables: SUPABASE_URL and SUPABASE_ANON_KEY
• This skill does NOT store credentials to disk
• This skill does NOT request or use the service role key
• All queries go through Supabase's RLS layer — the skill cannot bypass your security policies

API Calls

Use curl for all Supabase REST API operations:

Query (SELECT)

curl -s "[URL]/rest/v1/[table]?select=*&[filters]" \
  -H "apikey: [KEY]" \
  -H "Authorization: Bearer [KEY]"

Insert

curl -s -X POST "[URL]/rest/v1/[table]" \
  -H "apikey: [KEY]" \
  -H "Authorization: Bearer [KEY]" \
  -H "Content-Type: application/json" \
  -d '[JSON]'

Update

curl -s -X PATCH "[URL]/rest/v1/[table]?[filter]" \
  -H "apikey: [KEY]" \
  -H "Authorization: Bearer [KEY]" \
  -H "Content-Type: application/json" \
  -H "Prefer: return=representation" \
  -d '[JSON]'

Delete

curl -s -X DELETE "[URL]/rest/v1/[table]?[filter]" \
  -H "apikey: [KEY]" \
  -H "Authorization: Bearer [KEY]"

PostgREST Filter Syntax

• ?column=eq.value — equals
• ?column=neq.value — not equals
• ?column=gt.value — greater than
• ?column=lt.value — less than
• ?column=gte.value — greater than or equal
• ?column=like.*pattern* — LIKE
• ?column=ilike.*pattern* — case-insensitive LIKE
• ?column=in.(val1,val2) — IN
• ?column=is.null — IS NULL
• ?order=column.desc — ORDER BY
• ?limit=10 — LIMIT
• ?offset=20 — OFFSET
• ?select=col1,col2,related_table(col3) — select specific columns + joins