Supabase
Tools
| Name & Description | Type |
|---|---|
| SUPABASE_BETA_RUN_SQL_QUERYExecutes a given sql query against the project's database; use for advanced data operations or when standard API endpoints are insufficient, ensuring queries are valid postgresql and sanitized. | action |
| SUPABASE_CREATE_AN_ORGANIZATIONCreates a new Supabase organization, which serves as a top-level container for projects, billing, and team access. | action |
| SUPABASE_CREATE_A_PROJECTCreates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous. | action |
| SUPABASE_LIST_ALL_ORGANIZATIONSLists all organizations (id and name only) associated with the Supabase account, excluding project details within these organizations. | action |
| SUPABASE_LIST_ALL_PROJECTSRetrieves a list of all Supabase projects, including their id, name, region, and status, for the authenticated user. | action |
| SUPABASE_ALPHA_CREATES_A_NEW_API_KEY_FOR_THE_PROJECTCreates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized jwt templates. | action |
| SUPABASE_ALPHA_DELETES_AN_API_KEY_FOR_THE_PROJECTPermanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access. | action |
| SUPABASE_ALPHA_GET_A_THIRD_PARTY_INTEGRATIONRetrieves the detailed configuration for a specific third-party authentication (tpa) provider, identified by `tpa id`, within an existing Supabase project specified by `ref`. | action |
| SUPABASE_ALPHA_LISTS_ALL_THIRD_PARTY_AUTH_INTEGRATIONSLists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings. | action |
| SUPABASE_ALPHA_REMOVES_A_THIRD_PARTY_AUTH_INTEGRATIONRemoves a third-party authentication provider (e. | action |
| SUPABASE_ALPHA_UPDATES_AN_API_KEY_FOR_THE_PROJECTUpdates an existing Supabase project API key's `description` and/or `secret jwt template` (which defines its `role`); does not regenerate the key string. | action |
| SUPABASE_BETA_ACTIVATES_A_CUSTOM_HOSTNAME_FOR_A_PROJECTActivates a previously configured custom hostname for a Supabase project, assuming dns settings are verified externally. | action |
| SUPABASE_BETA_ACTIVATES_A_VANITY_SUBDOMAIN_FOR_A_PROJECTActivates a vanity subdomain for the specified Supabase project, requiring subsequent dns configuration for the subdomain to become operational. | action |
| SUPABASE_BETA_AUTHORIZE_USER_THROUGH_OAUTHGenerates a Supabase oauth 2. | action |
| SUPABASE_BETA_CHECKS_VANITY_SUBDOMAIN_AVAILABILITYChecks if a specific vanity subdomain is available for a Supabase project; this action does not reserve or assign the subdomain. | action |
| SUPABASE_BETA_ENABLES_DATABASE_WEBHOOKS_ON_THE_PROJECTEnables database webhooks for the Supabase project `ref`, triggering real-time notifications for insert, update, or delete events. | action |
| SUPABASE_BETA_GETS_CURRENT_VANITY_SUBDOMAIN_CONFIGFetches the current vanity subdomain configuration, including its status and custom domain name, for a Supabase project identified by its reference id. | action |
| SUPABASE_BETA_GETS_PROJECT_S_CUSTOM_HOSTNAME_CONFIGRetrieves a Supabase project's custom hostname configuration, including its status, ssl certificate, and ownership verification, noting that availability may depend on the project's plan. | action |
| SUPABASE_BETA_GETS_PROJECT_S_NETWORK_BANSRetrieves the list of banned ipv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation. | action |
| SUPABASE_BETA_GETS_PROJECT_S_NETWORK_RESTRICTIONSRetrieves the current network restriction settings (e. | action |
| SUPABASE_BETA_GETS_PROJECT_S_PGSODIUM_CONFIGRetrieves the pgsodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref`. | action |
| SUPABASE_BETA_GET_PROJECT_S_SSL_ENFORCEMENT_CONFIGURATIONRetrieves the ssl enforcement configuration for a specified Supabase project, indicating if ssl connections are mandated for its database. | action |
| SUPABASE_BETA_REMOVE_A_READ_REPLICAIrreversibly initiates the removal of a specified read replica from an existing Supabase project, confirming only the start of the process, not its completion. | action |
| SUPABASE_BETA_REMOVE_NETWORK_BANSRemoves specified ipv4 addresses from a Supabase project's network ban list, granting immediate access; ips not currently banned are ignored. | action |
| SUPABASE_BETA_SET_UP_A_READ_REPLICAProvisions a read-only replica for a Supabase project in a specified, Supabase-supported aws region to enhance read performance and reduce latency. | action |
| SUPABASE_BETA_UPDATES_PROJECT_S_NETWORK_RESTRICTIONSUpdates and applies network access restrictions (ipv4/ipv6 cidr lists) for a Supabase project, which may terminate existing connections not matching the new rules. | action |
| SUPABASE_BETA_UPGRADES_THE_PROJECT_S_POSTGRES_VERSIONInitiates an asynchronous upgrade of a Supabase project's postgresql database to a specified `target version` from a selected `release channel`, returning a `tracking id` to monitor status; the `target version` must be available in the chosen channel. | action |
| SUPABASE_CONFIG_PGSODIUM_UPDATE_WITH_ROOT_KEY_WARNINGCritically updates or initializes a Supabase project's pgsodium root encryption key for security setup or key rotation, requiring secure backup of the new key to prevent irreversible data loss. | action |
| SUPABASE_CREATES_A_NEW_SSO_PROVIDERCreates a new saml 2. | action |
| SUPABASE_CREATES_A_NEW_THIRD_PARTY_AUTH_INTEGRATIONCall this to add a new third-party authentication method (oidc or jwks) to a Supabase project for integrating external identity providers (e. | action |
| SUPABASE_CREATE_A_DATABASE_BRANCHCreates a new, isolated database branch from an existing Supabase project (identified by `ref`), useful for setting up separate environments like development or testing, which can optionally be linked to a git branch. | action |
| SUPABASE_CREATE_A_FUNCTIONCreates a new serverless edge function for a Supabase project (identified by `ref`), requiring valid javascript/typescript in `body` and a project-unique `slug 1` identifier. | action |
| SUPABASE_CUSTOM_HOSTNAME_DNS_VERIFICATIONRe-verifies dns and ssl configurations for an existing custom hostname associated with a Supabase project. | action |
| SUPABASE_DELETES_THE_GIVEN_PROJECTPermanently and irreversibly deletes a Supabase project, identified by its unique `ref` id, resulting in complete data loss. | action |
| SUPABASE_DELETE_A_DATABASE_BRANCHPermanently and irreversibly deletes a specific, non-default database branch by its `branch id`, without affecting other branches. | action |
| SUPABASE_DELETE_A_FUNCTIONPermanently deletes a specific edge function (by `function slug`) from a Supabase project (by `ref`); this action is irreversible and requires prior existence of both project and function. | action |
| SUPABASE_DELETE_CUSTOM_HOSTNAME_CONFIGDeletes an active custom hostname configuration for the project identified by `ref`, reverting to the default Supabase-provided hostname; this action immediately makes the project inaccessible via the custom domain and requires subsequent updates to client, oauth, and dns settings. | action |
| SUPABASE_DELETE_PROJECTS_VANITY_SUBDOMAINPermanently and irreversibly deletes an active vanity subdomain configuration for the specified Supabase project, reverting it to its default Supabase url. | action |
| SUPABASE_DISABLES_PREVIEW_BRANCHINGDisables the preview branching feature for an existing Supabase project, identified by its unique reference id (`ref`). | action |
| SUPABASE_DISABLE_PROJECT_READONLY_MODETemporarily disables a Supabase project's read-only mode for 15 minutes to allow write operations (e. | action |
| SUPABASE_EXCHANGE_AUTH_CODE(beta) implements the oauth 2. | action |
| SUPABASE_GENERATE_TYPE_SCRIPT_TYPESGenerates and retrieves typescript types from a Supabase project's database; any schemas specified in `included schemas` must exist in the project. | action |
| SUPABASE_GETS_A_SPECIFIC_SQL_SNIPPETRetrieves a specific sql snippet by its unique identifier. | action |
| SUPABASE_GETS_A_SSO_PROVIDER_BY_ITS_UUIDRetrieves the configuration details for a specific single sign-on (sso) provider (e. | action |
| SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATIONFetches comprehensive details for a specific Supabase organization using its unique slug. | action |
| SUPABASE_GETS_PROJECT_S_AUTH_CONFIGRetrieves the project's complete read-only authentication configuration, detailing all settings (e. | action |
| SUPABASE_GETS_PROJECT_S_POSTGREST_CONFIGRetrieves the postgrest configuration for a specific Supabase project. | action |
| SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIGRetrieves the current read-only postgresql database configuration for a specified Supabase project's `ref`, noting that some advanced or security-sensitive details might be omitted from the response. | action |
| SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUSRetrieves the current health status for a Supabase project, for specified services or all services if the 'services' list is omitted. | action |
| SUPABASE_GETS_PROJECT_S_SUPAVISOR_CONFIGRetrieves the supavisor (connection pooler) configuration for a specified Supabase project, identified by its reference id. | action |
| SUPABASE_GET_DATABASE_BRANCH_CONFIGRetrieves the read-only configuration and status for a Supabase database branch, typically for monitoring or verifying its settings. | action |
| SUPABASE_GET_PROJECT_API_KEYSRetrieves all API keys for an existing Supabase project, specified by its unique reference id (`ref`); this is a read-only operation. | action |
| SUPABASE_GET_PROJECT_S_PGBOUNCER_CONFIGRetrieves the active pgbouncer configuration (postgresql connection pooler) for a Supabase project, used for performance tuning, auditing, or getting the connection string. | action |
| SUPABASE_GET_PROJECT_UPGRADE_ELIGIBILITYChecks a Supabase project's eligibility for an upgrade, verifying compatibility and identifying potential issues; this action does not perform the actual upgrade. | action |
| SUPABASE_GET_PROJECT_UPGRADE_STATUSRetrieves the latest status of a Supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades. | action |
| SUPABASE_LISTS_ALL_BACKUPSLists all database backups for a Supabase project, providing details on existing backups but not creating new ones or performing restores; availability may depend on plan and configuration. | action |
| SUPABASE_LISTS_ALL_BUCKETSRetrieves a list of all storage buckets for a Supabase project, without returning bucket contents or access policies. | action |
| SUPABASE_LISTS_ALL_SSO_PROVIDERSLists all configured single sign-on (sso) providers for a Supabase project, requiring the project reference id (`ref`) of an existing project. | action |
| SUPABASE_LISTS_SQL_SNIPPETS_FOR_THE_LOGGED_IN_USERRetrieves a list of sql snippets for the logged-in user, optionally filtered by a specific Supabase project if `project ref` is provided. | action |
| SUPABASE_LIST_ALL_DATABASE_BRANCHESLists all database branches for a specified Supabase project, used for isolated development and testing of schema changes; ensure the project reference id is valid. | action |
| SUPABASE_LIST_ALL_FUNCTIONSLists metadata for all edge functions in a Supabase project (specified by 'ref'), excluding function code or logs; the project must exist. | action |
| SUPABASE_LIST_ALL_SECRETSRetrieves all secrets for a Supabase project using its reference id; secret values in the response may be masked. | action |
| SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATIONRetrieves all members of a Supabase organization, identified by its unique slug, including their user id, username, email, role, and mfa status. | action |
| SUPABASE_REMOVES_A_SSO_PROVIDER_BY_ITS_UUIDDeletes a specific sso provider by its id (`provider id`) from a Supabase project (`ref`), which disables it and returns its details; ensure this action will not inadvertently lock out users. | action |
| SUPABASE_RESETS_A_DATABASE_BRANCHResets an existing Supabase database branch, identified by `branch id`, to its initial clean state, irreversibly deleting all its current data and schema changes. | action |
| SUPABASE_RESTORES_A_PITR_BACKUP_FOR_A_DATABASERestores a Supabase project's database to a specific unix timestamp using point-in-time recovery (pitr), overwriting the current state; requires a paid plan with pitr and physical backups enabled. | action |
| SUPABASE_RETRIEVE_A_FUNCTIONRetrieves detailed information, metadata, configuration, and status for a specific edge function using its project reference id and function slug. | action |
| SUPABASE_RETRIEVE_A_FUNCTION_BODYRetrieves the source code (body) for a specified serverless edge function using its project reference and function slug; this is a read-only operation that does not execute the function or return runtime logs. | action |
| SUPABASE_RETURNS_PROJECT_S_READONLY_MODE_STATUSRetrieves the read-only mode status for a specified Supabase project to check its operational state; this action does not change the read-only state. | action |
| SUPABASE_UPDATES_A_SSO_PROVIDER_BY_ITS_UUIDUpdates an existing sso provider's saml metadata, associated email domains, or attribute mappings for a Supabase project, identified by `ref` and `provider id`. | action |
| SUPABASE_UPDATES_PROJECT_S_POSTGREST_CONFIGUpdates postgrest configuration settings (e. | action |
| SUPABASE_UPDATES_PROJECT_S_POSTGRES_CONFIGUpdates specified postgresql configuration parameters for an existing Supabase project (`ref`) to optimize database performance; note that unspecified parameters remain unchanged, and caution is advised as incorrect settings can impact stability or require a restart. | action |
| SUPABASE_UPDATES_PROJECT_S_SUPAVISOR_CONFIGUpdates the supavisor (database pooler) configuration, such as `default pool size`, for an existing Supabase project identified by `ref`; the `pool mode` parameter in the request is deprecated and ignored. | action |
| SUPABASE_UPDATE_A_FUNCTIONUpdates an existing Supabase edge function's properties (like name, slug, source code, jwt settings, import map) identified by project `ref` and `function slug`, supporting plain text code or eszip for the body. | action |
| SUPABASE_UPDATE_CUSTOM_HOSTNAMEUpdates the custom hostname for a Supabase project, requiring subsequent dns changes to a user-controlled domain for ssl certificate issuance and domain ownership. | action |
| SUPABASE_UPDATE_DATABASE_BRANCH_CONFIGUpdates the configuration of a Supabase database branch, allowing modification of its name, associated git branch, reset-on-push behavior, persistence, and status. | action |
| SUPABASE_UPDATE_SSL_ENFORCEMENT_CONFIGUpdates the ssl enforcement configuration (enable/disable) for a specified Supabase project's database. | action |