All connectors

Supabase

230 tools Developer Tools Databases

Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications

Open in SlashspaceDownload for Mac

Connect Supabase

  1. Open Slashspace and go to Settings, then Connectors.
  2. On Discover, search for Supabase and click Connect.
  3. Sign in to Supabase in your browser. Slashspace updates when the account is connected.
  4. Then ask for what you need in any Agent mode chat. Supabase is on in every chat unless you switch it off.

What your chats can do

230 tools from Supabase.

  • Accept Invite External Jit AccessAccept an invitation for JIT database access.
  • Create project api keyCreates a publishable or secret API key for an existing Supabase project, optionally with a description.
  • Delete an API key from the projectPermanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
  • Delete third party auth configRemoves a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.
  • 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`.
  • List third-party auth integrations for projectLists 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.
  • Update an API key for the projectUpdates the description of an existing Supabase project API key without regenerating the key string.
  • Append Resumable UploadAppend data to a TUS resumable upload. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Append Resumable Upload SignedAppend data to a signed resumable upload. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Apply a database migrationApplies a tracked SQL database migration to a Supabase project, for schema changes or other DDL/DML operations. You can provide a migration name, rollback SQL, and an idempotency key to help prevent duplicate tracking.
  • Apply Project AddonApply or update billing addons and compute instance size. Changes may affect billing; inspect the project plan before modifying addons.
  • Authorize Jit AccessAuthorize user-to-role mappings for JIT access.
  • Beta activate custom hostname for projectActivates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally.
  • Activate vanity subdomain for projectActivates a vanity subdomain for the specified Supabase project (e.g., 'my-brand.supabase.co'). Important notes: - Vanity subdomains require a paid plan (Pro/Team/Enterprise) - Usage of vanity subdomains and custom domains is mutually exclusive - After activation, your project's auth services will no longer work on the original {project-ref}.supabase.co hostname - Schedule a downtime window to update client code and OAuth providers before activating
  • Authorize user through OAuthRequests Supabase OAuth 2.0 authorization for a registered application and returns the redirect location when the endpoint responds with a redirect, or status and error information otherwise.
  • Check vanity subdomain availabilityChecks whether a vanity subdomain is available for a Supabase project without reserving or assigning it. The endpoint requires a Pro, Team, or Enterprise organization plan.
  • Setup read replica for projectProvisions a read-only replica for a Supabase project in a specified supported AWS region to enhance read performance and reduce latency. This beta feature requires a Pro, Team, or Enterprise organization plan.
  • Enable project database webhooksEnables database webhooks for the Supabase project `ref`, triggering real-time notifications for INSERT, UPDATE, or DELETE events.
  • Beta get 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.
  • Retrieve network bans for projectRetrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation.
  • Get project network restrictionsRetrieves a Supabase project's network restriction settings, including IPv4 and IPv6 CIDR allowlists, entitlement, and application status. The response may also include the previous configuration while a change is pending.
  • Get project pgsodium configRetrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref`.
  • Get project SSL enforcement configurationRetrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database.
  • Get current vanity subdomain configFetches the current vanity subdomain configuration for a Supabase project, including its status and any custom domain name. The endpoint requires a Pro, Team, or Enterprise organization plan.
  • Remove project network bansRemoves specified IPv4 addresses from a Supabase project's network ban list, granting immediate access; IPs not currently banned are ignored.
  • Remove read replicaInitiates removal of a specified read replica database from a Supabase project. This beta operation requires a valid replica identifier and permission to manage read replicas; redirect application traffic before removal.
  • Execute project database queryExecutes PostgreSQL queries against a Supabase project's database for data retrieval, modification, or schema operations. Read-only mode does not prevent detected INSERT, UPDATE, or DELETE statements from making changes.
  • Beta update project network restrictionsUpdates network access restrictions (IPv4/IPv6 CIDR lists) for a Supabase project. Changes may terminate existing connections that do not match the new rules; the returned status indicates whether the configuration is stored or applied.
  • Upgrade the project's PostgreSQL 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.
  • Cancel Project RestorationCancel project restoration.
  • Copy Storage ObjectCopy an object. Uses a secret/service-role project key and bypasses Row Level Security.
  • Count action runsCounts the number of action runs for a Supabase project using a HEAD request. Use this when you need to retrieve the total count of action runs without fetching the full list of runs.
  • Count Function ResultsCount rows from a known exposed table-valued function using HEAD, without a body. PostgREST enforces a read-only transaction; functions attempting database writes fail. Uses an elevated secret/service_role key that bypasses Row Level Security. OAuth requires secrets:read; fine-grained PATs require api_gateway_keys_read and api_gateway_keys_secret_read for project-key discovery. Not for scalar functions.
  • Count Table RowsCount matching rows in an exposed table or view without downloading rows. Uses an elevated secret/service-role key and bypasses Row Level Security. OAuth requires secrets:read; fine-grained personal access tokens require api_gateway_keys_read and api_gateway_keys_secret_read.
  • Create new projectCreates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous.
  • Bulk create secretsBulk creates secrets for a Supabase project. Secret names must not start with SUPABASE_; leading and trailing whitespace is stripped from names and values before submission.
  • 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.
  • 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` identifier.
  • Create CLI login roleCreates a temporary CLI login role for database access with specified permissions; use when setting up CLI authentication for development or administrative tasks.
  • Create an organizationCreates a new Supabase organization, which serves as a top-level container for projects, billing, and team access.
  • Create project signing keyCreate a new JWT signing key for a Supabase project, with an optional initial standby or in-use status.
  • Create Resumable UploadCreate a TUS resumable upload. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Create Resumable Upload SignedCreate a signed TUS resumable upload. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Create Signed Download UrlGenerate a time-limited download capability for an object. Uses privileged project-key discovery; protect the returned URL.
  • Create Signed Download UrlsGenerate time-limited download capabilities for multiple objects. Uses privileged project-key discovery; protect the returned URLs.
  • Create Signed Upload URLCreate a two-hour signed authorization for uploading a Storage object. OAuth connections need ``secrets:read``. Fine-grained personal access tokens need ``api_gateway_keys_read`` and ``api_gateway_keys_secret_read``.
  • Create SSO provider configurationCreates a new SAML 2.0 Single Sign-On (SSO) provider for a Supabase project, requiring either `metadata_xml` or `metadata_url` for SAML IdP configuration.
  • Create Storage BucketCreate a Storage bucket. Uses a secret/service-role project key and bypasses Row Level Security.
  • Create 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.g., for SSO); the API may also support `custom_jwks` if sent directly.
  • Delete all branchesDisables preview branching for a Supabase project, which deletes all remaining branches. IMPORTANT: Before calling this endpoint, you must manually delete all non-default branches. The API will reject the request with a 422 error if non-default branches exist. Use this action when you need to completely disable the preview branching feature for a project. This action is irreversible - all branches will be permanently removed and preview branching will be disabled. Requirements: - Preview branching must be enabled on the project - All non-default branches must be deleted first - Project must be on Pro plan or above to have preview branching
  • Delete Bucket LifecycleDelete bucket lifecycle configuration. Uses a secret/service-role project key and bypasses Row Level Security.
  • 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.
  • Delete branch by idPermanently and irreversibly deletes a specific, non-default database branch by its `branch_id`, without affecting other branches.
  • Delete edge functionDeletes an Edge Function from a Supabase project by its slug. Use this action when you need to permanently remove a deployed Edge Function that is no longer needed or should be replaced. This action is irreversible — the function cannot be recovered once deleted, though you can redeploy it from source if needed.
  • Delete an edge function by slugPermanently 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.
  • Delete Invite External Jit AccessDelete an external user's JIT invitation.
  • Delete Jit AccessDelete JIT access by user ID.
  • Delete CLI login roles[Beta] Deletes existing login roles used by the Supabase CLI for the specified project. Use when you need to remove CLI authentication roles that were previously created for project access.
  • Delete a projectPermanently and irreversibly deletes a Supabase project and all associated resources, including databases, storage, and configurations. This action is irreversible — the project cannot be recovered once deleted. Use when you need to completely remove a project from your organization.
  • Delete vanity subdomain for projectPermanently and irreversibly deletes an active vanity subdomain configuration for the specified Supabase project, reverting it to its default Supabase URL.
  • Bulk delete secretsDeletes one or more secrets from a Supabase project by their names. This action is irreversible - deleted secrets cannot be recovered. Use this action when you need to remove environment variables or configuration secrets that are no longer needed or should be replaced. Supports both single and bulk deletion operations through the same endpoint.
  • Remove an SSO providerDeletes 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.
  • Delete Storage BucketDelete a bucket. Uses a secret/service-role project key and bypasses Row Level Security.
  • Delete Storage ObjectDelete a Storage object. Uses a secret/service-role project key and bypasses Row Level Security.
  • Delete Storage ObjectsDelete multiple objects. Uses a secret/service-role project key and bypasses Row Level Security.
  • Delete Table RowsPermanently delete matching rows from an exposed Supabase table or view. Uses an elevated secret/service_role project key, bypassing Row Level Security. Requires filters unless allow_all_rows explicitly permits an unfiltered delete. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal the project key.
  • Deploy functionDeploys Edge Functions to a Supabase project using multipart upload.
  • Disable preview branchingDisables the preview branching feature for an existing Supabase project, identified by its unique reference ID (`ref`). Note: Preview branching must be enabled on the project for this operation to succeed. If the project does not have preview branching enabled, a 422 error will be returned.
  • Disable project readonly modeTemporarily disables a Supabase project's read-only mode for 15 minutes to allow write operations (e.g., for maintenance or critical updates), after which it automatically reverts to read-only.
  • Download private objectDownloads an object from a private Supabase Storage bucket and returns its bytes as base64 with selected metadata. Choose anon or service-role authorization; anon access requires an allowing storage policy, while service-role access bypasses row-level security. An object version and download filename can optionally be specified.
  • Download Public ObjectRetrieve an object from a public bucket.
  • Download Signed ObjectRetrieve an object using a presigned URL.
  • Download Storage ObjectRetrieve a Storage object. Uses a secret/service-role project key and bypasses Row Level Security.
  • Empty Storage BucketEmpty a bucket. Uses a secret/service-role project key and bypasses Row Level Security.
  • Exchange auth code for access and refresh token(Beta) Implements the OAuth 2.0 token endpoint to exchange an authorization code or refresh token for access/refresh tokens, based on `grant_type`. This is a standard OAuth 2.0 token endpoint that uses application/x-www-form-urlencoded content type as per OAuth 2.0 specification. Requires a valid registered OAuth application client_id and client_secret. For authorization_code grant type: - Requires valid authorization code obtained from the OAuth authorization flow - Optionally requires code_verifier if PKCE was used during authorization For refresh_token grant type: - Requires valid refresh_token from a previous token exchange
  • Generate TypeScript typesGenerates and retrieves TypeScript types from a Supabase project's database; any schemas specified in `included_schemas` must exist in the project.
  • Get action run statusRetrieves the status and details of a specific action run, including its steps, timestamps, and configuration. Use this to monitor or check the progress of an action execution.
  • Get action run logsRetrieves the execution logs for a specific action run by its ID. Use this to debug action executions, view output messages, and investigate errors that occurred during action runs.
  • Get project auth configRetrieves a Supabase project's authentication settings for read-only inspection, including supported provider configurations, MFA policies, email and SMS templates, security settings, and hooks. The returned configuration may not include every field supplied by the API.
  • Get Authenticated Image HeadersGet authenticated image transformation headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Authenticated Object HeadersRetrieve authenticated object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Authenticated Object InfoRetrieve authenticated object information. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Authenticated Object Info HeadersGet authenticated object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Available RegionsTool to get the list of available regions for creating a new Supabase project. Use when you need to determine which regions are available for project deployment, or to get region recommendations based on geographic location and instance size requirements. Note: This is a Beta endpoint.
  • Get Backup ScheduleGet the project's backup schedule.
  • Get a database branchRetrieves detailed information about a specific database branch by its name and project reference. Use this to check branch status, configuration, and metadata before performing operations on the branch.
  • Get Bucket LifecycleGet bucket lifecycle configuration. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Bucket Lifecycle HeadersGet bucket lifecycle response headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get database branch configRetrieves the read-only configuration and status for a Supabase database branch, typically for monitoring or verifying its settings.
  • Get Database DiskGet database disk attributes.
  • Get Database OpenapiGet the project's PostgREST OpenAPI specification.
  • Get Disk UtilizationGet disk utilization.
  • Retrieve a functionRetrieves detailed information, metadata, configuration, and status for a specific Edge Function using its project reference ID and function slug.
  • Retrieve a function bodyRetrieves the body of a specified Supabase Edge Function using its project reference and function slug. This read-only operation does not execute the function or return runtime logs.
  • Get API Health StatusChecks the Supabase API for availability, helping diagnose connectivity issues.
  • Get Jit AccessGet user-to-role mappings for JIT database access.
  • Get JIT access configRetrieves a Supabase project's just-in-time (JIT) access configuration state using the beta endpoint.
  • Get a migrationRetrieves a specific database migration entry from the migration history using its version identifier. Use when you need to inspect migration details, SQL statements, or rollback commands for a specific migration version.
  • Get information about an organizationFetches comprehensive details for a specific Supabase organization using its unique slug.
  • Get Organization EntitlementsGet organization entitlements.
  • Get ProfileGet the user's profile.
  • Get projectRetrieves detailed information about a Supabase project by reference ID, including its status, database configuration, organization, region, and creation timestamp. Requires a Management API bearer token with appropriate project read access.
  • Get project API keyRetrieves details of a specific API key for a Supabase project by its UUID. Use when you need to inspect a single key's configuration, type, or metadata.
  • 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.
  • Get project configRetrieve a project's consolidated effective database, pooler, Auth, Data API, Realtime, and Storage configuration. This Supabase Management API endpoint is Alpha and currently supports Personal Access Tokens (PATs) only; Supabase OAuth access tokens are not supported.
  • Get Project Disk Autoscale ConfigGet disk autoscale configuration.
  • Get Project Function Combined StatsGet combined function statistics.
  • Get project logsRetrieves the unified logs stream for a Supabase project, including database, API, and edge function logs, for monitoring and debugging. Custom queries use ClickHouse SQL against the logs table, filtering by source; legacy source tables and metadata joins must be migrated. Provide both UTC timestamps for a time window; Supabase documents a last-minute fallback without both and a maximum 24-hour range. Check the response's error field even when execution reports success. Returned row fields depend on the query.
  • Get project metricsRetrieve a Supabase project's Prometheus/OpenMetrics exposition.
  • Get project PgBouncer configRetrieves the active PgBouncer configuration (PostgreSQL connection pooler) for a Supabase project, used for performance tuning, auditing, or getting the connection string.
  • Get project 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.
  • Get project's PostgREST configRetrieves the PostgREST configuration for a specific Supabase project.
  • Get project's read-only 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.
  • Get project signing keysTool to list all signing keys for a Supabase project. Use when you need to retrieve JWT signing keys for authentication verification or rotation management.
  • Get project Supavisor configurationRetrieves the Supavisor (connection pooler) configuration for a specified Supabase project, identified by its reference ID.
  • 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.
  • Get project upgrade statusRetrieves the latest status of a Supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades.
  • Get Project Usage Api CountGet project usage API counts.
  • Get Project Usage Request CountGet project usage API request counts.
  • Get Public Image HeadersGet public image transformation headers.
  • Get Public Object HeadersGet public object information headers.
  • Get Public Object InfoGet public object information.
  • Get Realtime ConfigGet Realtime configuration.
  • Get TUS resumable upload base optionsHandles OPTIONS request for TUS Resumable uploads to discover server capabilities. Use when preparing resumable upload requests to verify supported TUS protocol versions and extensions.
  • Get TUS resumable upload optionsHandles OPTIONS request for TUS Resumable uploads to discover server capabilities. Use when preparing resumable upload requests to verify supported TUS protocol versions and extensions.
  • Get Resumable Upload StatusGet resumable upload offset and metadata. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Get Resumable Upload Status SignedGet signed resumable upload offset and metadata. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Get Signed Image HeadersGet signed image transformation headers.
  • Get Signed Object HeadersGet headers for a presigned object retrieval.
  • Get project's auth configRetrieves a project's authentication configuration, including provider, MFA, email, SMS, JWT and security settings. The response can contain sensitive secrets.
  • Get 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.
  • Get a specific SQL snippetRetrieves a specific SQL snippet by its unique identifier.
  • Get a SSO provider by its UUIDRetrieves configuration details for a project's SAML Single Sign-On provider by UUID.
  • Get Storage BucketGet bucket details. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Storage Bucket HeadersGet bucket response headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Storage Bucket List HeadersGet bucket-list response headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Storage ConfigGet project Storage configuration.
  • Get Storage HealthCheck the Storage service health, distinct from Management API health.
  • Get Storage Health HeadersGet Storage service health response headers.
  • Get Storage Object HeadersRetrieve object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Storage Object InfoRetrieve object information. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Storage Object Info HeadersGet object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
  • Get Table SchemasRetrieve column details, types, primary and unique constraints, and optionally foreign keys for multiple database tables. Some returned metadata uses placeholders, and index information is not fetched.
  • OPTIONS for resumable upload signSend an OPTIONS request to the TUS resumable upload signing endpoint.
  • OPTIONS for resumable upload signSend an OPTIONS request to a TUS resumable upload signing endpoint for a specified path.
  • Insert Table RowsInsert rows or upsert on primary/UNIQUE keys in an exposed table or view. Uses a secret or service_role project key and bypasses Row Level Security. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal project keys. Upserts can overwrite data.
  • Invite External Jit AccessInvite an external user for JIT database access.
  • Invoke Database FunctionInvoke a known exposed Postgres function with named JSON arguments. Supports custom exposed schemas and table-valued result selection, filters, ordering, pagination, and counts. The function runs with a service-role project key that bypasses Row Level Security and may create, update, or delete data or execute DDL.
  • Invoke Edge FunctionTool to invoke a deployed Supabase Edge Function over HTTPS. Use for testing and debugging Edge Functions with configurable method, headers, body, and authentication.
  • Invoke Read Only FunctionInvoke a known exposed Postgres function using GET in a read-only transaction. Not an Edge Function or arbitrary SQL executor. Database writes are rejected by PostgREST's GET transaction mode. Uses a secret/service_role key that bypasses Row Level Security, so reads can expose all rows. External side effects of a function are not prevented by a database read-only transaction. Supports table-valued projection, filters, ordering, pagination, and counts. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal project keys.
  • List Action RunsList one page of action runs for a project.
  • List all organizationsLists organizations associated with the authenticated Supabase account, returning their IDs, slugs, and names.
  • List all projectsLists Supabase projects for the authenticated user, including project ID, name, organization ID, region, status, database information, and creation time. OAuth access requires the projects:read scope.
  • List project database 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.
  • List database branchesLists all database branches for a specified Supabase project, providing information about each branch's status, configuration, and metadata. Use this action when you need to view all branches in a project, check branch statuses, or identify available branches before performing operations. Database branches are useful for isolated development and testing of schema changes.
  • List all bucketsRetrieves a list of all storage buckets for a Supabase project, without returning bucket contents or access policies.
  • 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.
  • List all functionsLists metadata for all Edge Functions in a Supabase project (specified by 'ref'), excluding function code or logs; the project must exist.
  • List Jit AccessList all user-to-role mappings for JIT access.
  • List migration historyRetrieves the list of applied database migration versions for a Supabase project. Use this to track which migrations have been applied to the project's database. This is a read-only operation that requires the project reference ID.
  • 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.
  • List Organization ProjectsList one page of projects for an organization.
  • List Project AddonsList billing addons and compute instance selections. Changes may affect billing; inspect the project plan before modifying addons.
  • List Project Restore VersionsList available restore versions for a project.
  • List project secretsRetrieves all secrets (environment variables) for a Supabase project by its reference ID. Use this action when you need to view the secrets configured for a project, such as API keys, database URLs, or other environment variables. Note that secret values in the response may be masked for security reasons.
  • List all secretsRetrieves all secrets for a Supabase project using its reference ID; secret values in the response may be masked.
  • List SQL snippets for the logged in userRetrieves the first page of SQL snippets for the logged-in user, optionally filtered by Supabase project. The response may contain a pagination cursor, but this tool cannot request subsequent pages.
  • List all SSO providersLists all configured Single Sign-On (SSO) providers for a Supabase project, requiring the project reference ID (`ref`) of an existing project.
  • List Storage BucketsList Storage buckets through the data-plane API. Uses a secret/service-role project key and bypasses Row Level Security.
  • List Storage ObjectsSearch for objects under a prefix. Uses a secret/service-role project key and bypasses Row Level Security.
  • List Storage Objects V2Search for objects under a prefix using list v2. Uses a secret/service-role project key and bypasses Row Level Security.
  • List Database TablesLists tables and optionally views in Supabase database schemas, providing an overview of database structure. Schema discovery can fall back to public, and per-schema failures are reported alongside any partial results.
  • Merge a database branchInitiates a merge of a database branch into its target database. An optional migration version can limit how far migrations are merged; the response identifies the triggered workflow run.
  • Modify Database DiskModify database disk configuration.
  • Move Storage ObjectMove an object. Uses a secret/service-role project key and bypasses Row Level Security.
  • Oauth Authorize Project ClaimInitiate OAuth authorization to claim a project. Returns redirect responses without following them; continue the browser flow using headers.location. An authorization redirect does not prove the claim has completed.
  • Patch a migration[Beta] Patches an existing entry in the project's migration history, updating the name or rollback script. Use this to correct migration metadata after the migration has been created.
  • Patch project network restrictionsUpdates project's network restrictions by incrementally adding or removing IPv4/IPv6 CIDR blocks. Use when you need to modify existing restrictions without replacing the entire configuration.
  • Pause ProjectPause a project, making its services unavailable until it is restored.
  • Post Resumable UploadCreate a TUS upload through the wildcard creation route (an alias of base POST). Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Post Resumable Upload SignedCreate a signed TUS upload through the wildcard creation route (an alias of base POST). Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Purge Bucket CachePurge cache for a bucket or its transformations. Uses a secret/service-role project key and bypasses Row Level Security.
  • Purge Object CachePurge cache for an object or its transformations. Uses a secret/service-role project key and bypasses Row Level Security.
  • Purge Storage CachePurge cache for the tenant or tenant transformations. Uses a secret/service-role project key and bypasses Row Level Security.
  • Push a database branchPushes a database branch, applying migrations and changes to the specified branch. Use when you need to deploy schema changes or migrations to a database branch.
  • Remove Project AddonRemove billing addons or revert compute sizing. Changes may affect billing; inspect the project plan before modifying addons.
  • Render Authenticated ImageRender an authenticated image with transformations. Uses a secret/service-role project key and bypasses Row Level Security.
  • Render Public ImageRender a public image with transformations.
  • Render Signed ImageRender a signed image with transformations.
  • Replace Bucket LifecycleReplace bucket lifecycle configuration. Uses a secret/service-role project key and bypasses Row Level Security.
  • Reset 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.
  • Restart ProjectRestart a project, temporarily interrupting its services. Newly provisioned projects must wait ten minutes.
  • Restore BranchRestore a scheduled branch deletion.
  • Restore database PITR backupRestores 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.
  • Restore ProjectRestore the given project.
  • Rollback MigrationsRollback database migrations and remove them from history.
  • Execute read-only database queryRun a read-only SQL query against a Supabase project as supabase_read_only_user. This beta endpoint requires all entity references to be schema-qualified.
  • Select From TableSelect rows from a Supabase/PostgREST table or view, with column selection, filtering, sorting, and pagination. When a project API key is not supplied, the tool may use a service-role key, which bypasses row-level security.
  • Shutdown RealtimeShut down the project Realtime service connections, disconnecting active clients.
  • Terminate Resumable UploadTerminate a TUS resumable upload. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Terminate Resumable Upload SignedTerminate a signed resumable upload. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
  • Update Action Run StatusUpdate the status of an action run.
  • Update a functionUpdates an existing Supabase Edge Function's properties, including its name, slug, source code, JWT settings, and import map, using its project reference and function slug.
  • Update API keyUpdates an existing Supabase project API key's name, description, or JWT template without regenerating the key. It can request that the key value be revealed in the response.
  • Update Backup ScheduleUpdate the project's backup schedule.
  • Update branch configurationUpdates the configuration of a Supabase database branch, allowing modification of its name, associated Git branch, notification URL, persistence settings, and status. Use this action when you need to modify branch settings after creation, such as linking to a different Git branch, changing the branch name, or updating persistence behavior. Note: Database branching requires a paid Supabase plan (Pro or higher).
  • Update database branch configUpdates a Supabase database branch's configuration, including its name, associated Git branch, persistence, and status. The reset-on-push field is deprecated and ignored by Supabase.
  • Update database passwordUpdates the database password for a Supabase project. Use it to rotate credentials or recover database access.
  • Bulk update functionsBulk updates Edge Functions in a Supabase project with configurations such as status and version. The operation can create new functions or replace existing ones; version increments must be supplied manually.
  • Update Jit AccessUpdate a user mapping for JIT access.
  • Update JIT access config[Beta] Update a Supabase project's just-in-time (JIT) access configuration. Use to enable or disable JIT access features for privileged operations on the project.
  • Update pgsodium root keyUpdates a Supabase project's pgsodium root encryption key. Changing the root key can make data encrypted with the previous key inaccessible.
  • Update a projectUpdates a Supabase project's configuration (currently supports updating the project name). Use when you need to rename an existing project.
  • Update project's auth configUpdate Supabase project Auth configuration via the Management API. Use to fix misconfigured Auth redirects, SMTP settings, or other auth parameters. Only provided fields are updated; others remain unchanged. Before updating, confirm the Auth service status is ACTIVE_HEALTHY by checking project health.
  • Update project's custom hostname configurationUpdates the custom hostname for a Supabase project, requiring subsequent DNS changes for SSL certificate issuance and domain ownership. API errors may be returned in an error message field.
  • Update project legacy API keysDeprecated by the provider; no sunset date or replacement is announced. Disable or re-enable JWT-based legacy API keys (anon, service_role). The endpoint may return HTTP 404 when unavailable. Behavior is unchanged.
  • Update 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.
  • Update project's PostgREST configUpdates PostgREST configuration settings (e.g., `max_rows`, `db_pool`, `db_schema`, `db_extra_search_path`) for a Supabase project to fine-tune API performance, data exposure, and database resource usage.
  • Update database pooler configUpdates Supavisor (database pooler) configuration, including default pool size and pool mode, for an existing Supabase project identified by its reference.
  • Update Realtime ConfigUpdate Realtime configuration.
  • Update SSL enforcement configUpdates the SSL enforcement configuration (enable/disable) for a specified Supabase project's database.
  • Update an 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`.
  • Update Storage BucketUpdate bucket properties. Uses a secret/service-role project key and bypasses Row Level Security.
  • Update Storage ConfigUpdate project Storage configuration.
  • Update Storage ObjectUpdate the object at an existing key. Uses a secret/service-role project key and bypasses Row Level Security.
  • Update Table RowsUpdate matching rows in an exposed Supabase table or updatable view. Uses a secret or service_role project key, bypassing Row Level Security. PostgREST warns that unfiltered PATCH updates every row: filters are required unless allow_all_rows=true. Filters can still match every row; check them carefully. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal the project key.
  • Upload Signed ObjectUpload an object using a presigned URL.
  • Upload Storage ObjectUpload a new object. Uses a secret/service-role project key and bypasses Row Level Security.
  • Upsert migrationTool to upsert a database migration without applying it. Use when you need to track migration changes for a project. [Beta] This endpoint stores migration metadata without executing the SQL.
  • Reverify custom hostnameRe-verifies DNS and SSL configurations for an existing custom hostname associated with a Supabase project.