Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | { |
| 2 | "slug": "toolkits-supabase", |
| 3 | "title": "Supabase", |
| 4 | "description": "Public support knowledge for Supabase.", |
| 5 | "articlePath": "toolkits-supabase.md", |
| 6 | "sources": [ |
| 7 | { |
| 8 | "sourcePath": "toolkits/supabase/public.md", |
| 9 | "sourceHeading": "Supabase authorization is usually organization-scoped" |
| 10 | }, |
| 11 | { |
| 12 | "sourcePath": "toolkits/supabase/public.md", |
| 13 | "sourceHeading": "Supabase API-key connections pass `supabase_personal_token` during connected account creation" |
| 14 | }, |
| 15 | { |
| 16 | "sourcePath": "toolkits/supabase/public.md", |
| 17 | "sourceHeading": "Supabase supports both OAuth2 and API_KEY auth through Composio APIs" |
| 18 | }, |
| 19 | { |
| 20 | "sourcePath": "toolkits/supabase/public.md", |
| 21 | "sourceHeading": "Supabase MCP in Cursor may need an explicit initiate-connection step" |
| 22 | }, |
| 23 | { |
| 24 | "sourcePath": "toolkits/supabase/public.md", |
| 25 | "sourceHeading": "`SUPABASE_BETA_RUN_SQL_QUERY` is still available when configured in an MCP server" |
| 26 | }, |
| 27 | { |
| 28 | "sourcePath": "toolkits/supabase/public.md", |
| 29 | "sourceHeading": "Hosted Supabase should use `https://api.supabase.com` as base URL, not the project URL" |
| 30 | }, |
| 31 | { |
| 32 | "sourcePath": "toolkits/supabase/public.md", |
| 33 | "sourceHeading": "Self-hosted Supabase requires toolkit support for a custom base URL" |
| 34 | }, |
| 35 | { |
| 36 | "sourcePath": "toolkits/supabase/public.md", |
| 37 | "sourceHeading": "Configure Supabase Management API scopes on the Supabase OAuth app" |
| 38 | }, |
| 39 | { |
| 40 | "sourcePath": "toolkits/supabase/public.md", |
| 41 | "sourceHeading": "Supabase permission errors are often provider-side access-control failures" |
| 42 | }, |
| 43 | { |
| 44 | "sourcePath": "toolkits/supabase/public.md", |
| 45 | "sourceHeading": "Diagnose Supabase rate limits from the underlying error" |
| 46 | } |
| 47 | ], |
| 48 | "topics": [ |
| 49 | "auth-config", |
| 50 | "authentication", |
| 51 | "errors-and-troubleshooting", |
| 52 | "sessions-and-execution", |
| 53 | "toolkits-and-providers" |
| 54 | ], |
| 55 | "tags": [ |
| 56 | "for-you", |
| 57 | "platform", |
| 58 | "supabase" |
| 59 | ], |
| 60 | "aliases": [ |
| 61 | "/kb/toolkits/supabase-troubleshooting", |
| 62 | "composio-does-not-enforce-hard-service-rate-limits-check-the-underlyin", |
| 63 | "cursor-mcp-server-name-length-limits-can-break-supabase-mcp", |
| 64 | "hosted-supabase-should-use-https-api-supabase-com-as-base-url-not-the", |
| 65 | "limit-supabase-scopes-in-the-customer-s-oauth-app-not-through-composio", |
| 66 | "self-hosted-supabase-requires-toolkit-support-for-a-custom-base-url", |
| 67 | "supabase-api-key-connections-pass-supabase-personal-token-during-conne", |
| 68 | "supabase-authorization-is-usually-organization-scoped", |
| 69 | "supabase-beta-run-sql-query-is-still-available-when-configured-in-an-m", |
| 70 | "supabase-mcp-in-cursor-may-need-an-explicit-initiate-connection-step", |
| 71 | "supabase-permission-errors-are-often-provider-side-access-control-fail", |
| 72 | "supabase-supports-both-oauth2-and-api-key-auth-through-composio-apis", |
| 73 | "supabase-troubleshooting" |
| 74 | ], |
| 75 | "relatedGuides": [], |
| 76 | "externalResources": [], |
| 77 | "updatedAt": "2026-06-24", |
| 78 | "lastVerifiedAt": "2026-08-17", |
| 79 | "reviewAfter": "2026-11-15", |
| 80 | "freshness": "evergreen", |
| 81 | "state": "published", |
| 82 | "featured": false |
| 83 | } |