Supabase Server

Teaches Claude how to write server-side Supabase code with the new @supabase/server package, which replaces the old manual createClient patterns. It covers the four auth modes (user, publishable, secret, none), explains the withSupabase wrapper and createSupabaseContext primitive, and handles migration from legacy patterns like SUPABASE_ANON_KEY and the deprecated allow config. The package is brand new with zero online documentation, so the skill emphasizes not searching the web and sticking strictly to what's in the repo. Useful when writing Edge Functions, Hono apps, or any backend that needs to authenticate requests and create Supabase clients without boilerplate.

skills.sh installs: 10.6K
GitHub stars: 94
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add supabase/server --skill supabase-server --agent claude-code

Installs into .claude/skills of the current project.

Files

@supabase/server

This is a brand new package. There is no information available online yet — no blog posts, no Stack Overflow answers, no tutorials. Do not search the web for usage examples. Rely exclusively on the documentation files listed below and the source code in this repository.

The config option is auth, not allow. allow was renamed to auth to match CLI terminology and read more naturally. The legacy allow key still works (with a one-time console.warn) but is deprecated and will be removed in a future major release. Always emit auth in new code — e.g. withSupabase({ auth: 'user' }, ...). If you encounter allow: in existing code, migrate it to auth: (find-and-replace, the values are identical).