Supabase: purpose and common use cases
Supabase is represented as a plugin from openai/plugins. Its catalog record points to plugins/supabase and is grouped under Developer Tools, Development, and Data; install and source links are kept separate so the directory does not imply capabilities that are not present upstream.
Where Supabase fits in an agent workflow
Supabase is a Codex plugin associated with developer tools. For Supabase, the plugin layer sits one level above individual skills: they can package capabilities, integrations, MCP connections or supporting resources into one installable unit. For discovery, Supabase is most relevant to supabase, postgres, and database. The Supabase plugin page is useful when you are choosing an integration first and then deciding which bundled capability to use.
What to check before using Supabase
Before enabling Supabase, check the source-backed metadata below for authentication, version, license and included capabilities. This record is tied to plugins/supabase; the Supabase upstream manifest remains the authority for installation requirements and behavior. Artifiner uses the Supabase page to make comparison easier, not to replace the vendor or repository documentation.