# Supabase Your Toolhouse AI Worker can connect to Supabase using 121 specialized tools. ## Auth Connection This service requires an auth connection to use its tools. You can set this up in your Toolhouse dashboard under [Auth Connections](https://toolhouse.app/auth-connections?authkit_slugs=supabase). ## Tools (121) ### `Supabase Alpha Create Api Key` Integration name: **SUPABASE\_ALPHA\_CREATE\_API\_KEY** Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | — | The unique reference ID of the Supabase project. | | `name` | string | ✅ | — | Name for the API key. Must start with a lowercase letter or underscore, followed only by lowercase alphanumeric characters or underscores. Example: 'my\_api\_key\_01'. | | `type` | string | ✅ | `"publishable"` | Specifies the type of API key: 'publishable' for client-side use or 'secret' for server-side operations. | | `description` | string | | — | Optional human-readable description for the API key. | *** ### `Supabase Alpha Delete Api Key` Integration name: **SUPABASE\_ALPHA\_DELETE\_API\_KEY** Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ---------------------------------------------------------------------------------------- | | `id` | string | ✅ | `"your-api-key-id"` | The unique identifier of the API key that needs to be deleted from the project. | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project from which the API key is to be deleted. | *** ### `Supabase Alpha Delete Third Party Auth Integration` Integration name: **SUPABASE\_ALPHA\_DELETE\_THIRD\_PARTY\_AUTH\_INTEGRATION** Removes 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------------------- | -------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project. | | `tpa_id` | string | ✅ | `"30879943-2772-4a11-ae54-92cb7f0d71e8"` | The unique identifier (ID) of the third-party authentication provider configuration to be removed. | *** ### `Supabase Alpha Get Third Party Integration` Integration name: **SUPABASE\_ALPHA\_GET\_THIRD\_PARTY\_INTEGRATION** Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------------------- | ---------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique identifier (reference) of the Supabase project. | | `tpa_id` | string | ✅ | `"123e4567-e89b-12d3-a456-426614174000"` | The unique identifier of the specific third-party authentication provider configuration to retrieve. | *** ### `Supabase Alpha List Third Party Auth Integrations` Integration name: **SUPABASE\_ALPHA\_LIST\_THIRD\_PARTY\_AUTH\_INTEGRATIONS** Lists 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ---------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique identifier of the Supabase project. | *** ### `Supabase Alpha Update Api Key` Integration name: **SUPABASE\_ALPHA\_UPDATE\_API\_KEY** Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | -------------------------------------- | ----------------------------------------------------------------------------- | | `id` | string | ✅ | `"api_key_123456789"` | The unique identifier of the API key that needs to be updated. | | `ref` | string | ✅ | `"project_abc123xyz"` | The unique reference ID of the Supabase project to which the API key belongs. | | `description` | string | | `"Updated key for primary API access"` | Optional new description for the API key. | *** ### `Supabase Apply A Migration` Integration name: **SUPABASE\_APPLY\_A\_MIGRATION** Tool to apply database migrations to a Supabase project. Use when you need to execute SQL schema changes, create tables, alter columns, or run other DDL/DML operations as part of a tracked migration. This is a Beta feature in the Supabase Management API. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------ | :------: | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project (e.g., 'pamqaklsszmjzugtywow'). Found in Project Settings > General > Reference ID. | | `name` | string | | `"add_users_table"` | A unique name for the migration to track it in the migration history. If not provided, a default name will be assigned. | | `query` | string | ✅ | `"CREATE TABLE users (id SERIAL PRIMARY KEY, name TEXT NOT NULL);"` | The SQL migration query to execute against the project's database. Must be at least 1 character long. | | `rollback` | string | | `"DROP TABLE users;"` | Optional SQL query to rollback/undo this migration if needed. | | `idempotency_key` | string | | `"migration-2024-01-15-001"` | A unique key to ensure the same migration is tracked only once. If provided, prevents duplicate migrations with the same key from being applied. | *** ### `Supabase Beta Activate Custom Hostname` Integration name: **SUPABASE\_BETA\_ACTIVATE\_CUSTOM\_HOSTNAME** Activates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------- | ----------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-supabase-id"` | The unique identifier (project ID) of the Supabase project. | *** ### `Supabase Beta Activate Vanity Subdomain` Integration name: **SUPABASE\_BETA\_ACTIVATE\_VANITY\_SUBDOMAIN** Activates 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 #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------ | :------: | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | — | Unique reference ID of the Supabase project. | | `vanity_subdomain` | string | ✅ | `"my-example-brand"` | Vanity subdomain to activate (e.g., 'my-example-brand'). Must be 1-63 alphanumeric characters or hyphens; cannot start or end with a hyphen. | *** ### `Supabase Beta Authorize User Through Oauth` Integration name: **SUPABASE\_BETA\_AUTHORIZE\_USER\_THROUGH\_OAUTH** Generates a Supabase OAuth 2.0 authorization URL for user redirection. IMPORTANT: This action requires a pre-registered OAuth client\_id and a redirect\_uri that matches one of the pre-registered URIs for that OAuth application. Without a valid registered OAuth application, this endpoint will return a 400 error. To use this action: 1. Register an OAuth application in the Supabase dashboard 2. Use the client\_id from the registered application 3. Ensure redirect\_uri matches one of the registered callback URLs #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------------- | ------ | :------: | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `scope` | string | | `"email profile"` | Space-separated list of OAuth scopes for requested permissions on user resources (e.g., 'email profile', 'storage.objects.read'). | | `state` | string | | `"csrf-token-value-12345"` | Opaque value to maintain state between request and callback; returned unmodified to aid CSRF prevention. | | `client_id` | string | ✅ | `"your-supabase-client-id-abc-123"` | Unique identifier for the OAuth client application, registered with Supabase. Must be a valid client\_id from a registered OAuth application. | | `redirect_uri` | string | ✅ | `"https://yourapp.com/oauth/callback"` | URI where Supabase redirects the user after authorization; must exactly match a registered URI for the client application. | | `response_mode` | string | | `"query"` | Specifies how authorization response parameters are returned (e.g., 'query', 'fragment', 'form\_post'). Default is determined by `response_type` if not specified. | | `response_type` | string | ✅ | `"code"` | Specifies the authorization flow type: 'code' for Authorization Code Grant; 'token' for Implicit Grant (access token); 'id\_token token' for OIDC hybrid flows (ID and access tokens). | | `code_challenge` | string | | `"E9Melhoa2OwvFrEMTJguCHaoeK1t8URWbuGJSstw-cM"` | PKCE code challenge to secure authorization code grants, typically a BASE64URL-encoded SHA256 hash of `code_verifier`. | | `code_challenge_method` | string | | `"S256"` | Method to derive `code_challenge` for PKCE: 'S256'/'sha256' for SHA256 hashing; 'plain' sends verifier as is (not for production if hashing possible). Required if `code_challenge` is provided. | *** ### `Supabase Beta Check Vanity Subdomain Availability` Integration name: **SUPABASE\_BETA\_CHECK\_VANITY\_SUBDOMAIN\_AVAILABILITY** Checks if a specific vanity subdomain is available for a Supabase project; this action does not reserve or assign the subdomain. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------ | :------: | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"your-project-ref-example"` | The unique reference ID of the Supabase project. | | `vanity_subdomain` | string | ✅ | `"my-cool-app"` | The desired vanity subdomain to check for availability (e.g., 'my-app'). Must be 1-63 alphanumeric characters or hyphens; cannot start or end with a hyphen. | *** ### `Supabase Beta Create Read Replica` Integration name: **SUPABASE\_BETA\_CREATE\_READ\_REPLICA** Provisions a read-only replica for a Supabase project in a specified, Supabase-supported AWS region to enhance read performance and reduce latency. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | -------------------- | -------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | Unique reference ID of the Supabase project. | | `read_replica_region` | string | ✅ | `"ap-northeast-1"` | AWS region for the read replica; selecting one closer to users improves performance and reduces latency. | *** ### `Supabase Beta Enable Database Webhooks` Integration name: **SUPABASE\_BETA\_ENABLE\_DATABASE\_WEBHOOKS** Enables database webhooks for the Supabase project `ref`, triggering real-time notifications for INSERT, UPDATE, or DELETE events. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ----------------------------------------------- | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | The unique identifier for the Supabase project. | *** ### `Supabase Beta Get Project Custom Hostname Config` Integration name: **SUPABASE\_BETA\_GET\_PROJECT\_CUSTOM\_HOSTNAME\_CONFIG** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------- | ---------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"ab12cd34ef56gh78ij90klmn"` | The unique reference ID of the Supabase project. This ID can typically be found in your project's dashboard URL. | *** ### `Supabase Beta Get Project Network Bans` Integration name: **SUPABASE\_BETA\_GET\_PROJECT\_NETWORK\_BANS** Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique project reference identifier for the Supabase project. Must be a valid 20-character project ref. You can retrieve valid project refs using the 'List all projects' action. | *** ### `Supabase Beta Get Project Network Restrictions` Integration name: **SUPABASE\_BETA\_GET\_PROJECT\_NETWORK\_RESTRICTIONS** Retrieves the network restriction settings (IP allowlists) for a Supabase project. Use this action to: - Check which IPv4/IPv6 CIDR blocks are allowed to connect to the project's database - Verify if network restrictions are enabled (entitlement: "allowed") or disabled ("disallowed") - Audit current network security configuration - Check if network restrictions have been modified (old\_config present) Note: Default values 0.0.0.0/0 (IPv4) and ::/0 (IPv6) mean all IPs are allowed. Network restrictions require a Pro, Team, or Enterprise plan. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | The unique project reference ID (also called project ID or ref). This is a 20-character alphanumeric string that identifies the Supabase project. Can be found in the project URL or retrieved via SUPABASE\_LIST\_ALL\_PROJECTS. | *** ### `Supabase Beta Get Project Pgsodium Config` Integration name: **SUPABASE\_BETA\_GET\_PROJECT\_PGSODIUM\_CONFIG** Retrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref`. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ---------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique identifier of the Supabase project. | *** ### `Supabase Beta Get Project Ssl Enforcement Config` Integration name: **SUPABASE\_BETA\_GET\_PROJECT\_SSL\_ENFORCEMENT\_CONFIG** Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-1"` | The unique identifier of the Supabase project. This can typically be found in your project's dashboard URL (e.g., `https://supabase.com/dashboard/project/`). | *** ### `Supabase Beta Get Vanity Subdomain Config` Integration name: **SUPABASE\_BETA\_GET\_VANITY\_SUBDOMAIN\_CONFIG** Fetches the current vanity subdomain configuration, including its status and custom domain name, for a Supabase project identified by its reference ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | The unique reference ID of the Supabase project for which to fetch the vanity subdomain configuration. | *** ### `Supabase Beta Remove Network Bans` Integration name: **SUPABASE\_BETA\_REMOVE\_NETWORK\_BANS** Removes specified IPv4 addresses from a Supabase project's network ban list, granting immediate access; IPs not currently banned are ignored. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------ | :------: | ---------------------------------- | --------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-example"` | The unique reference ID of the Supabase project. | | `ipv4_addresses` | array | ✅ | `["198.51.100.10","203.0.113.45"]` | A list of IPv4 addresses to be removed from the project's network ban list. | *** ### `Supabase Beta Remove Read Replica` Integration name: **SUPABASE\_BETA\_REMOVE\_READ\_REPLICA** Remove a read replica from a Supabase project (Pro plan or higher required). This beta endpoint initiates the removal of a specified read replica database. The operation is irreversible. Before removal, ensure all application traffic is redirected from the replica to the primary database. Requirements: - Project must be on Pro plan or higher - Bearer token with infra\_read\_replicas\_write permission (FGA) - Valid read replica database identifier Note: Returns 201 on success with an empty response body. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | The unique project reference ID (20 lowercase characters, e.g. 'abcdefghijklmnopqrst'). Found in project settings or URL. | | `database_identifier` | string | ✅ | `"read-replica-us-east-1-abc123"` | The unique identifier of the read replica database to remove. Obtain from the project's database settings or read replica listing. | *** ### `Supabase Beta Run Sql Query` Integration name: **SUPABASE\_BETA\_RUN\_SQL\_QUERY** Executes 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. Use the get\_table\_schemas or generate\_type\_script\_types tool to retrieve the table schema, then base your query on it. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------- | :------: | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | The unique reference ID of the Supabase project (used in the URL path). Must be exactly 20 lowercase letters (a-z). Can be found in Project Settings > General > Reference ID in the Supabase Dashboard, or from the dashboard URL: . Can also be provided as 'project\_ref'. | | `query` | string | ✅ | `"SELECT * FROM users WHERE id = 1;"` | The SQL query to be executed against the project's database. Can also be provided as 'sql'. CRITICAL - Single Quote Handling: Single quotes that delimit SQL string literals (e.g., 'John', '3 days') work normally when transmitted via JSON. However, apostrophes and single quotes WITHIN string content MUST be escaped using PostgreSQL's standard escaping (doubling the quote: ''). Examples: ✓ CORRECT: SELECT 'I''m here' (apostrophe in content is escaped as '') ✓ CORRECT: INSERT INTO users (bio) VALUES ('She said ''hello''') ✓ CORRECT: SELECT '{ "msg": "I''m ready" }'::jsonb (apostrophe inside JSON string is escaped) ✗ WRONG: SELECT 'I'm here' (syntax error - apostrophe breaks the string) ✗ WRONG: SELECT '{ "msg": "I'm ready" }'::jsonb (syntax error in JSON content) IMPORTANT - PostgreSQL Array Syntax: For columns of type text\[], integer\[], etc., do NOT use JSON array syntax like '\["item1", "item2"]' as PostgreSQL will reject it. Use PostgreSQL array syntax instead: (1) ARRAY constructor: ARRAY\['item1', 'item2'], or (2) Curly brace literal: '{"item1", "item2"}'. IMPORTANT - PostgreSQL Configuration Parameters: To reference Supabase secrets or config parameters, use current\_setting() with the correct parameter name (e.g., current\_setting('app.settings.my\_secret')). Parameter names must not contain sanitization placeholders like '', '\', etc. Note: Complex DDL operations (CREATE TABLE with multiple indexes, CREATE VIEW with joins, large data migrations) may timeout if they exceed the Supabase API's internal timeout limit (\~60 seconds). For long-running operations, consider breaking them into smaller queries or using a direct database connection. | | `read_only` | boolean | | `true` | If true, executes the query in a read-only transaction. Useful for safety when only fetching data without modifying the database. IMPORTANT: This parameter is incompatible with data modification statements. For INSERT, UPDATE, and DELETE statements, if set to true, it will be automatically overridden to false to allow the operation to proceed. For DDL statements (CREATE, ALTER, DROP, etc.), read\_only=true will cause an error - you must set it to false or omit it. | *** ### `Supabase Beta Update Project Network Restrictions` Integration name: **SUPABASE\_BETA\_UPDATE\_PROJECT\_NETWORK\_RESTRICTIONS** Updates and applies network access restrictions (IPv4/IPv6 CIDR lists) for a Supabase project, which may terminate existing connections not matching the new rules. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------ | :------: | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"your-project-ref"` | Unique reference ID of the Supabase project. | | `dbAllowedCidrs` | array | | `["192.168.1.1/32","10.0.0.0/8"]` | List of IPv4 addresses or CIDR notations for database access; `[]` removes all IPv4 restrictions, `null`/omitted leaves current IPv4 restrictions unchanged. | | `dbAllowedCidrsV6` | array | | `["2001:0db8::/32","2a00:1450:4001:801::200e"]` | List of IPv6 addresses or CIDR notations for database access; `[]` removes all IPv6 restrictions, `null`/omitted leaves current IPv6 restrictions unchanged. | *** ### `Supabase Beta Upgrade Project Postgres Version` Integration name: **SUPABASE\_BETA\_UPGRADE\_PROJECT\_POSTGRES\_VERSION** Initiates 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------ | :------: | ------------------------ | ----------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-123"` | The project's unique reference ID. | | `target_version` | string | ✅ | `"15.1.0.123"` | Target PostgreSQL version (e.g., '15.1.0.123'); must be available in the specified `release_channel`. | | `release_channel` | string | ✅ | `"alpha"` | Release channel for selecting the PostgreSQL version. | *** ### `Supabase Count Action Runs` Integration name: **SUPABASE\_COUNT\_ACTION\_RUNS** Counts 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. | *** ### `Supabase Create A Project` Integration name: **SUPABASE\_CREATE\_A\_PROJECT** Creates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------------- | ------- | :------: | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | `"my-awesome-app"` | Name for the new project; must be unique within the organization and not contain dots. | | `plan` | string | | `"free"` | Subscription plans (now set at the organization level). | | `region` | string | ✅ | `"us-east-1"` | Geographical region for the project's server and database. | | `db_pass` | string | ✅ | `"your_db_password_here"` | Password for the new database (required). Must be a secure password. IMPORTANT: Store this password securely as it cannot be retrieved later via the API and is needed for direct database connections. | | `kps_enabled` | boolean | | `true` | Deprecated and ignored. | | `template_url` | string | | `"https://github.com/supabase/supabase/tree/master/examples/nextjs-todo-list"` | Optional URL to a Supabase project template (e.g., from Git) to initialize the project. | | `organization_id` | string | ✅ | `"abcdefgh-1234-5678-abcd-1234567890ab"` | The actual organization ID or slug from your Supabase account. IMPORTANT: 'personal' is NOT a valid value - you must use the real organization ID returned by the 'List All Organizations' API endpoint (GET /v1/organizations) or found in your Supabase dashboard settings. | | `postgres_engine` | string | | `"15"` | Supported major versions of the PostgreSQL engine. | | `release_channel` | string | | `"ga"` | Available release channels for Supabase software. | | `desired_instance_size` | string | | `"micro"` | Available compute instance sizes for a Supabase project. | *** ### `Supabase Create Bulk Secrets` Integration name: **SUPABASE\_CREATE\_BULK\_SECRETS** Tool to bulk create secrets for a Supabase project. Use when you need to create multiple project secrets at once. Each secret name must not start with SUPABASE\_. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (ref) of the Supabase project where secrets will be created. | | `secrets` | array | ✅ | `[{"name":"DATABASE_URL","value":"postgresql://..."},{"name":"API_KEY","value":"sk_test_..."}]` | List of secrets to create. Each secret must have a unique name that doesn't start with SUPABASE\_. | *** ### `Supabase Create Database Branch` Integration name: **SUPABASE\_CREATE\_DATABASE\_BRANCH** Creates 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------------- | ------- | :------: | -------------------- | ------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the parent Supabase project. | | `region` | string | | `"us-east-1"` | Geographical region for the new database branch. | | `git_branch` | string | | `"main"` | Git branch name to associate with this database branch, linking database states to code branches. | | `persistent` | boolean | | `"true"` | Specifies if the branch is persistent (true) or ephemeral (false); ephemeral branches might be auto-deleted. | | `branch_name` | string | ✅ | `"staging-branch"` | A unique name for the new database branch. | | `postgres_engine` | string | | `"15"` | Desired PostgreSQL engine version for the new branch. | | `release_channel` | string | | `"ga"` | Release channel for Supabase features on this branch, determining feature stability. | | `desired_instance_size` | string | | `"micro"` | Compute instance size for the new database branch. | *** ### `Supabase Create Function` Integration name: **SUPABASE\_CREATE\_FUNCTION** Creates a new serverless Edge Function for a Supabase project (identified by `ref`), requiring valid JavaScript/TypeScript in `body` and a project-unique `slug` identifier. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------- | :------: | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | — | Project's unique identifier (path parameter). | | `body` | string | ✅ | `"export default async (req: Request) => { console.log(\"Hello from Edge Functions!\"); return new Response(\"Hello, World!\"); }"` | JavaScript or TypeScript source code for the Edge Function. | | `name` | string | ✅ | `"My Custom Function"` | Human-readable name for the function. | | `slug` | string | ✅ | `"my-custom-function"` | URL-friendly identifier for the function's route prefix. Must be unique within the project. | | `import_map` | boolean | | — | If true, enable import map for ES module resolution. | | `verify_jwt` | boolean | | — | If true, verify JWT in Authorization header before invoking the function. Set to false for public endpoints like webhooks. | | `entrypoint_path` | string | | `"./main.ts"` | Path to main function code, relative to project's functions directory. Defaults to `./index.ts` or `./index.js` in function's slug directory. | | `import_map_path` | string | | `"./import_map.json"` | Path to import map JSON, relative to project's functions directory; used if `import_map` is true. Defaults to `import_map.json` in function's slug directory. | *** ### `Supabase Create Login Role` Integration name: **SUPABASE\_CREATE\_LOGIN\_ROLE** Creates a temporary CLI login role for database access with specified permissions; use when setting up CLI authentication for development or administrative tasks. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------- | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | Project reference ID (unique identifier for the Supabase project). | | `read_only` | boolean | ✅ | `true` | Whether the login role should have read-only permissions. Set to true for read-only access, false for full access. | *** ### `Supabase Create Organization` Integration name: **SUPABASE\_CREATE\_ORGANIZATION** Creates a new Supabase organization, which serves as a top-level container for projects, billing, and team access. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ---------------------------------- | | `name` | string | ✅ | `"Acme Corporation"` | The name for the new organization. | *** ### `Supabase Create Project Signing Key` Integration name: **SUPABASE\_CREATE\_PROJECT\_SIGNING\_KEY** Create a new signing key for JWT authentication in a Supabase project. The key is created in standby status by default and must be activated separately. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project. Can also be provided as 'project\_ref'. | | `status` | string | | — | Status of a signing key in request. | | `algorithm` | string | ✅ | `"HS256"` | The cryptographic algorithm to use for the signing key. HS256 is recommended for most use cases. | *** ### `Supabase Create Sso Provider` Integration name: **SUPABASE\_CREATE\_SSO\_PROVIDER** Creates 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------------- | ------ | :------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | Unique reference ID of the Supabase project. | | `type` | string | ✅ | — | Type of the SSO provider; 'saml' (SAML 2.0) is the only supported value. | | `domains` | array | | `["example.com","another-example.org"]` | Email domains to associate with this SSO provider; users from these domains will be directed here for authentication. | | `metadata_url` | string | | `"https://my-idp.com/saml/metadata"` | URL to fetch SAML 2.0 metadata XML. Provide this or `metadata_xml`. | | `metadata_xml` | string | | `"'''...'''"` | SAML 2.0 metadata XML document as a string. Provide this or `metadata_url`. | | `attribute__mapping__keys` | object | | `"'''{\"email\": {\"names\": [\"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress\", \"mail\"]}, \"full_name\": {\"name\": \"displayName\"}, \"roles\": {\"name\": \"groups\", \"array\": true, \"default\": [\"user\"]}}'''"` | Maps SAML assertion attributes to custom Supabase JWT claims. Keys are JWT claim names; values specify SAML attribute extraction rules (e.g., `name`, `names`, `default`, `array`). | *** ### `Supabase Create Third Party Auth Integration` Integration name: **SUPABASE\_CREATE\_THIRD\_PARTY\_AUTH\_INTEGRATION** Call 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------ | :------: | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | — | The unique identifier of the Supabase project. | | `jwks_url` | string | | `"https://your-oidc-provider.com/.well-known/jwks.json"` | URL of the JSON Web Key Set (JWKS) for public key verification. Required if `oidc_issuer_url` is not provided. | | `oidc_issuer_url` | string | | `"https://your-oidc-provider.com/.well-known/openid-configuration"` | URL of the OpenID Connect (OIDC) issuer. Required if `jwks_url` is not provided. | *** ### `Supabase Delete Custom Hostname Config` Integration name: **SUPABASE\_DELETE\_CUSTOM\_HOSTNAME\_CONFIG** Deletes 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project for which the custom hostname configuration will be deleted. | *** ### `Supabase Delete Database Branch` Integration name: **SUPABASE\_DELETE\_DATABASE\_BRANCH** Permanently and irreversibly deletes a specific, non-default database branch by its `branch_id`, without affecting other branches. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ------------------------- | ----------------------------------------------------------- | | `branch_id` | string | ✅ | `"br_adjb2971mcran283mc"` | The unique identifier of the database branch to be deleted. | *** ### `Supabase Delete Function` Integration name: **SUPABASE\_DELETE\_FUNCTION** Permanently 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-reference-id"` | The unique identifier of the Supabase project from which the function will be deleted. | | `function_slug` | string | ✅ | `"my-custom-function"` | The unique identifier (slug) of the Edge Function to be deleted. This is typically the name given to the function upon creation. | *** ### `Supabase Delete Login Roles` Integration name: **SUPABASE\_DELETE\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique project reference identifier for the Supabase project from which CLI login roles will be deleted. | *** ### `Supabase Delete Project` Integration name: **SUPABASE\_DELETE\_PROJECT** Permanently and irreversibly deletes a Supabase project, identified by its unique `ref` ID, resulting in complete data loss. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | -------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"abcdefgh1234567890ab"` | Unique reference ID of the Supabase project to delete, typically a short alphanumeric string assigned upon creation. | *** ### `Supabase Delete Project Vanity Subdomain` Integration name: **SUPABASE\_DELETE\_PROJECT\_VANITY\_SUBDOMAIN** Permanently and irreversibly deletes an active vanity subdomain configuration for the specified Supabase project, reverting it to its default Supabase URL. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------ | | `ref` | string | ✅ | `"zcueounpgcpchreuvcrr"` | The unique reference ID of the Supabase project. | *** ### `Supabase Delete Secrets` Integration name: **SUPABASE\_DELETE\_SECRETS** Tool to bulk delete secrets from a Supabase project. Use when you need to remove multiple secrets at once. Requires the edge\_functions\_secrets\_write scope. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------ | :------: | ----------------------------------- | --------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (ref) of the Supabase project whose secrets should be deleted. | | `secret_names` | array | ✅ | `["TEST_SECRET_1","TEST_SECRET_2"]` | List of secret names to delete. Each name must match an existing secret in the project. | *** ### `Supabase Delete Sso Provider` Integration name: **SUPABASE\_DELETE\_SSO\_PROVIDER** Deletes 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | --------------------------- | --------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique identifier for your Supabase project. | | `provider_id` | string | ✅ | `"sso-provider-uuid-12345"` | The unique identifier (UUID) of the SSO provider to be removed. | *** ### `Supabase Deploy Function` Integration name: **SUPABASE\_DEPLOY\_FUNCTION** Deploys Edge Functions to a Supabase project using multipart upload. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"takovelbhvoqnvfmnhaq"` | Supabase project reference ID (e.g. `qftqfrxipqlzcmjcatfc`). | | `file` | object | | — | File uploaded to Composio (via SDK/MCP). Supports both single TypeScript/JavaScript files and pre-built .zip archives. Use this for large files, binary content, or complex multi-file functions. NOTE: Provide ONLY ONE of file\_content, file\_url, or file - not multiple. | | `slug` | string | | `"send-invitation-email"` | Slug of the function to deploy. | | `file_url` | string | | `"https://raw.githubusercontent.com/user/repo/main/functions/my-function/index.ts"` | Public URL to download the function code from. Supports GitHub raw URLs and other publicly accessible file URLs. NOTE: Provide ONLY ONE of file\_content, file\_url, or file - not multiple. | | `bundleOnly` | boolean | | — | If true, only bundle the function without publishing it. | | `file_content` | string | | `"export default () => new Response('Hello from Supabase!')"` | Raw TypeScript/JavaScript source code as a string. Ideal for simple functions or when code is generated dynamically. NOTE: Provide ONLY ONE of file\_content, file\_url, or file - not multiple. | *** ### `Supabase Disable Preview Branching` Integration name: **SUPABASE\_DISABLE\_PREVIEW\_BRANCHING** Disables 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ----------------------- | ---------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-id"` | The unique reference ID of the Supabase project for which preview branching is to be disabled. | *** ### `Supabase Disable Project Readonly` Integration name: **SUPABASE\_DISABLE\_PROJECT\_READONLY** Temporarily 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | --------------------------- | -------------------------------------------- | | `ref` | string | ✅ | `"your-unique-project-ref"` | Unique reference ID of the Supabase project. | *** ### `Supabase Exchange Oauth Token` Integration name: **SUPABASE\_EXCHANGE\_OAUTH\_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 #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | `code` | string | | `"authorization_code_from_provider"` | Authorization code from the server; required if `grant_type` is 'authorization\_code'. | | `client_id` | string | ✅ | `"your_app_client_id"` | Application's client ID. | | `grant_type` | string | ✅ | `"authorization_code"` | OAuth 2.0 grant type that dictates the token exchange flow. | | `redirect_uri` | string | | `"https://yourapp.com/callback"` | Redirect URI from the initial authorization; required if `grant_type` is 'authorization\_code' and it was part of the original request. | | `client_secret` | string | ✅ | `"your_app_client_secret"` | Application's client secret. | | `code_verifier` | string | | `"s256_code_challenge_verifier"` | PKCE code verifier; required if PKCE was used with an 'authorization\_code' grant type. | | `refresh_token` | string | | `"previously_issued_refresh_token"` | Refresh token for acquiring a new access token; required if `grant_type` is 'refresh\_token'. | *** ### `Supabase Generate Typescript Types` Integration name: **SUPABASE\_GENERATE\_TYPESCRIPT\_TYPES** Generates and retrieves TypeScript types from a Supabase project's database; any schemas specified in `included_schemas` must exist in the project. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------ | :------: | ----------------------------- | --------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your_supabase_project_ref"` | The unique reference ID of the Supabase project for which to generate TypeScript types. | | `included_schemas` | string | | `"public"` | Comma-separated database schema names to include in the generated TypeScript types. | *** ### `Supabase Get Action Run` Integration name: **SUPABASE\_GET\_ACTION\_RUN** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------------------ | ------------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project. Must be exactly 20 lowercase alphanumeric characters. | | `run_id` | string | ✅ | `"7e3058b0b64a41c38bf8579ad9ff2c4c"` | The unique identifier of the action run to retrieve. | *** ### `Supabase Get Action Run Logs` Integration name: **SUPABASE\_GET\_ACTION\_RUN\_LOGS** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project. This is visible in your Supabase project URL (e.g., ). | | `run_id` | string | ✅ | `"04d35a348ca049839c96cfa45653c9de"` | The unique identifier for the action run. This is returned when an action is triggered or can be retrieved from the actions list. | *** ### `Supabase Get Available Regions` Integration name: **SUPABASE\_GET\_AVAILABLE\_REGIONS** Tool 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------------- | ------ | :------: | ---------- | ----------------------------------------------------------------------------------------------- | | `continent` | string | | `"NA"` | Continent codes for regional recommendations. | | `organization_slug` | string | ✅ | `"my-org"` | Slug of your organization. This is required to retrieve available regions for project creation. | | `desired_instance_size` | string | | `"nano"` | Available instance sizes for Supabase projects. | *** ### `Supabase Get Branch` Integration name: **SUPABASE\_GET\_BRANCH** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference identifier (project ref) of the parent Supabase project. This ID can be found in your project's dashboard URL. | | `name` | string | ✅ | `"test-branch-fix"` | The unique name of the database branch to retrieve (e.g., 'test-branch-fix', 'staging', 'feature-x'). | *** ### `Supabase Get Database Branch Config` Integration name: **SUPABASE\_GET\_DATABASE\_BRANCH\_CONFIG** Retrieves the read-only configuration and status for a Supabase database branch, typically for monitoring or verifying its settings. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------- | | `branch_id` | string | ✅ | `"abcdefghijklmnopqrst"` | Project reference (ref) for the database branch. Must be exactly 20 lowercase alphabetic characters. | *** ### `Supabase Get Database Metadata` Integration name: **SUPABASE\_GET\_DATABASE\_METADATA** Gets database metadata for the given project. Returns information about databases, schemas, and tables structure. Note: This endpoint is deprecated and may be removed in future versions. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | Project ref. The unique reference ID of the Supabase project (visible in your Supabase project URL). | *** ### `Supabase Get Function` Integration name: **SUPABASE\_GET\_FUNCTION** Retrieves detailed information, metadata, configuration, and status for a specific Edge Function using its project reference ID and function slug. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"hukthtzjnedrudwkbdqa"` | The unique reference ID of the Supabase project. Must be exactly 20 lowercase alphanumeric characters (letters a-z and digits 0-9 only, no hyphens, underscores, or special characters). You can find this in your Supabase project URL (e.g., ) or by using the 'List all projects' API. | | `function_slug` | string | ✅ | `"my-edge-function"` | The unique identifier (slug) for the Edge Function. | *** ### `Supabase Get Function Body` Integration name: **SUPABASE\_GET\_FUNCTION\_BODY** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-123"` | The unique reference ID of the Supabase project. | | `function_slug` | string | ✅ | `"my-custom-function-slug"` | The unique identifier (slug) of the serverless Edge Function whose body is to be retrieved. This is typically the function's name. | *** ### `Supabase Get Health` Integration name: **SUPABASE\_GET\_HEALTH** Tool to check the health status of the Supabase API. Use when you need to verify API availability or troubleshoot connectivity issues. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Supabase Get Jit Access Config` Integration name: **SUPABASE\_GET\_JIT\_ACCESS\_CONFIG** \[Beta] Retrieves the project's just-in-time (JIT) access configuration, including user roles and their expiration settings. Use this to check temporary access grants and their validity periods. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project. Can also be provided as 'project\_ref'. | *** ### `Supabase Get Legacy Signing Key` Integration name: **SUPABASE\_GET\_LEGACY\_SIGNING\_KEY** Retrieves the signing key information for the JWT secret imported as signing key for this project. This endpoint is deprecated and will be removed in the future; check for HTTP 404 Not Found which indicates the endpoint is no longer available. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. | *** ### `Supabase Get Migration` Integration name: **SUPABASE\_GET\_MIGRATION** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project. Must be exactly 20 lowercase alphanumeric characters (letters a-z and digits 0-9 only, no hyphens, underscores, or special characters). You can find this in your Supabase project URL (e.g., ) or by using the 'List all projects' API. | | `version` | string | ✅ | `"20260216042751"` | The version identifier of the migration to fetch. Typically a timestamp-based identifier (e.g., '20260216042751'). | *** ### `Supabase Get Organization` Integration name: **SUPABASE\_GET\_ORGANIZATION** Fetches comprehensive details for a specific Supabase organization using its unique slug. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------ | -------------------------------------------------------- | | `slug` | string | ✅ | `"my-awesome-org"` | The unique, URL-friendly identifier of the organization. | *** ### `Supabase Get Performance Advisors` Integration name: **SUPABASE\_GET\_PERFORMANCE\_ADVISORS** Retrieves project performance advisors for a Supabase project. Returns a list of performance lints that identify potential issues and optimization opportunities. Note: This endpoint is deprecated. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. The project must belong to the authenticated user. | *** ### `Supabase Get Project` Integration name: **SUPABASE\_GET\_PROJECT** Retrieves detailed information about a specific Supabase project by its unique reference ID. Use when you need to get comprehensive project details including status, database configuration, and metadata. Authentication: - Requires a valid Bearer token in the Authorization header. - Token format: 'Bearer \' where access\_token is either: - A Personal Access Token (PAT) generated from - An OAuth2 access token with the 'project\_admin\_read' scope Required Scope: - project\_admin\_read: Allows retrieval of project information. Returns: Project object containing id, ref, name, organization details, region, status, database configuration, and created\_at timestamp. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | -------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | Project ref - unique identifier (20 lowercase letters) for the Supabase project. | *** ### `Supabase Get Project Api Key` Integration name: **SUPABASE\_GET\_PROJECT\_API\_KEY** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | string | ✅ | `"f74f2b01-7e3b-48c6-a33d-45d2205c904a"` | UUID of the API key (must be UUID format from publishable/secret type keys, not legacy key names like 'anon' or 'service\_role'). You can get this ID from the List Project API Keys action. | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. | | `reveal` | boolean | | — | If true, reveals the full API key value in the response. If false or omitted, secret key values will be partially redacted. Per Supabase's security model, secrets are hidden by default. | *** ### `Supabase Get Project Api Keys` Integration name: **SUPABASE\_GET\_PROJECT\_API\_KEYS** Retrieves all API keys for an existing Supabase project, specified by its unique reference ID (`ref`); this is a read-only operation. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"trfgquxorjaqlumyxocw"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. The project must belong to the authenticated user. | | `reveal` | boolean | | — | If true, reveals the full API key values in the response. If false or omitted, secret key values will be partially redacted. Per Supabase's security model, secrets are hidden by default. | *** ### `Supabase Get Project Legacy Api Keys` Integration name: **SUPABASE\_GET\_PROJECT\_LEGACY\_API\_KEYS** Checks whether JWT-based legacy API keys (anon, service\_role) are enabled for a Supabase project. This API endpoint is deprecated and may be removed in the future (returns HTTP 404 Not Found when unavailable). #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. The project must belong to the authenticated user. | *** ### `Supabase Get Project Logs` Integration name: **SUPABASE\_GET\_PROJECT\_LOGS** Retrieves analytics logs for a Supabase project. Use this to fetch and analyze project logs including edge function logs, database logs, and API logs for monitoring and debugging. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. | | `sql` | string | | — | Custom SQL query to execute on the logs. Allows filtering, aggregation, and transformation of log data. See Supabase docs for querying logs for more details. | | `iso_timestamp_end` | string | | — | End timestamp for filtering logs in ISO 8601 format (e.g., '2024-01-31T23:59:59Z'). Only logs before or at this timestamp will be included. | | `iso_timestamp_start` | string | | — | Start timestamp for filtering logs in ISO 8601 format (e.g., '2024-01-01T00:00:00Z'). Only logs on or after this timestamp will be included. | *** ### `Supabase Get Project Pgbouncer Config` Integration name: **SUPABASE\_GET\_PROJECT\_PGBOUNCER\_CONFIG** Retrieves the active PgBouncer configuration (PostgreSQL connection pooler) for a Supabase project, used for performance tuning, auditing, or getting the connection string. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | -------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique ID of the Supabase project. | *** ### `Supabase Get Project Postgres Config` Integration name: **SUPABASE\_GET\_PROJECT\_POSTGRES\_CONFIG** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ------------------------------------------------ | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project. | *** ### `Supabase Get Project Postgrest Config` Integration name: **SUPABASE\_GET\_PROJECT\_POSTGREST\_CONFIG** Retrieves the PostgREST configuration for a specific Supabase project. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ---------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique identifier of the Supabase project. | *** ### `Supabase Get Project Readonly Mode Status` Integration name: **SUPABASE\_GET\_PROJECT\_READONLY\_MODE\_STATUS** Retrieves the read-only mode status for a specified Supabase project to check its operational state; this action does not change the read-only state. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | --------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-abc"` | Project reference ID, found in your project's dashboard URL (e.g., `https://supabase.com/dashboard/project/`). | *** ### `Supabase Get Project Signing Keys` Integration name: **SUPABASE\_GET\_PROJECT\_SIGNING\_KEYS** Tool to list all signing keys for a Supabase project. Use when you need to retrieve JWT signing keys for authentication verification or rotation management. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"trfgquxorjaqlumyxocw"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. | *** ### `Supabase Get Project Supavisor Config` Integration name: **SUPABASE\_GET\_PROJECT\_SUPAVISOR\_CONFIG** Retrieves the Supavisor (connection pooler) configuration for a specified Supabase project, identified by its reference ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ------------------------------------------------ | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project. | *** ### `Supabase Get Project Upgrade Eligibility` Integration name: **SUPABASE\_GET\_PROJECT\_UPGRADE\_ELIGIBILITY** Checks a Supabase project's eligibility for an upgrade, verifying compatibility and identifying potential issues; this action does not perform the actual upgrade. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | Unique identifier of the Supabase project (e.g., 'opntiysxcrktmaarzjhz'). Can be obtained from the Supabase dashboard URL or by listing all projects. | *** ### `Supabase Get Project Upgrade Status` Integration name: **SUPABASE\_GET\_PROJECT\_UPGRADE\_STATUS** Retrieves the latest status of a Supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ------------------------------------------------ | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project. | *** ### `Supabase Get Resumable Upload Base Options` Integration name: **SUPABASE\_GET\_RESUMABLE\_UPLOAD\_BASE\_OPTIONS** Handles OPTIONS request for TUS Resumable uploads to discover server capabilities. Use when preparing resumable upload requests to verify supported TUS protocol versions and extensions. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Supabase Get Resumable Upload Options` Integration name: **SUPABASE\_GET\_RESUMABLE\_UPLOAD\_OPTIONS** Handles OPTIONS request for TUS Resumable uploads to discover server capabilities. Use when preparing resumable upload requests to verify supported TUS protocol versions and extensions. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `wildcard` | string | ✅ | `"test-upload-id"` | The wildcard path parameter representing the upload ID or file path for the TUS resumable upload. Used to identify the specific upload resource for CORS preflight requests. | *** ### `Supabase Get Security Advisors` Integration name: **SUPABASE\_GET\_SECURITY\_ADVISORS** Retrieves security advisor findings and recommendations for a Supabase project. Use when you need to audit project security posture, identify SQL-based security issues, or get remediation guidance. Note: This endpoint is deprecated and may be removed in future API versions. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. | | `lint_type` | string | | — | Type of linting to perform for security advisors. | *** ### `Supabase Gets Project S Auth Config` Integration name: **SUPABASE\_GETS\_PROJECT\_S\_AUTH\_CONFIG** Retrieves the project's complete read-only authentication configuration, detailing all settings (e.g., providers, MFA, email/SMS, JWT, security policies) but excluding sensitive secrets. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ---------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project. Can also be provided as 'project\_ref'. | *** ### `Supabase Gets Project S Service Health Status` Integration name: **SUPABASE\_GETS\_PROJECT\_S\_SERVICE\_HEALTH\_STATUS** Retrieves the current health status for a Supabase project, for specified services or all services if the 'services' list is omitted. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | — | The unique identifier (ref) of the Supabase project. | | `services` | array | | `"auth"` | A list of specific services for which to retrieve health status. If omitted, returns health status for all services. Valid values: auth, db, db\_postgres\_user, pg\_bouncer, pooler, realtime, rest, storage. | *** ### `Supabase Get Sql Snippet` Integration name: **SUPABASE\_GET\_SQL\_SNIPPET** Retrieves a specific SQL snippet by its unique identifier. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | --------------------- | ----------------------------------------------------- | | `id` | string | ✅ | `"snippet_abc123xyz"` | The unique identifier of the SQL snippet to retrieve. | *** ### `Supabase Get Sso Provider` Integration name: **SUPABASE\_GET\_SSO\_PROVIDER** Retrieves the configuration details for a specific Single Sign-On (SSO) provider (e.g., SAML, Google, GitHub, Azure AD), identified by its UUID, within a Supabase project. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ---------------------------------------- | -------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | The unique reference ID of the Supabase project. | | `provider_id` | string | ✅ | `"123e4567-e89b-12d3-a456-426614174000"` | The unique identifier (UUID) of the SSO provider whose configuration is to be fetched. | *** ### `Supabase Get Table Schemas` Integration name: **SUPABASE\_GET\_TABLE\_SCHEMAS** Retrieves column details, types, and constraints for multiple database tables to help debug schema issues and write accurate SQL queries. Use the SUPABASE\_LIST\_TABLES action first to discover available tables, the fetch their detailed schemas. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------------- | ------- | :------: | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `project_ref` | string | ✅ | `"huqmqtilymjtstzxbuww"` | The unique reference ID of the Supabase project. This is visible in your Supabase project URL (e.g., ). | | `table_names` | array | ✅ | `["users","posts","comments"]` | List of table names to retrieve schemas for. At least one table name is required (empty lists are not allowed). Tables can be from different schemas (e.g., 'public.users', 'operations.call\_queue\_items'). Without schema prefix, 'public' is assumed. Maximum 20 tables per request. | | `include_indexes` | boolean | | — | Whether to include index information in the response | | `exclude_null_values` | boolean | | — | Whether to exclude properties with null values from the response for cleaner output | | `include_relationships` | boolean | | — | Whether to include foreign key relationships in the response | *** ### `Supabase Handle Resumable Upload Sign Options` Integration name: **SUPABASE\_HANDLE\_RESUMABLE\_UPLOAD\_SIGN\_OPTIONS** Handles CORS preflight OPTIONS request for TUS resumable upload signing. Use when preparing cross-origin resumable upload requests to verify allowed methods and headers. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Supabase Handle Resumable Upload Sign Options With Id` Integration name: **SUPABASE\_HANDLE\_RESUMABLE\_UPLOAD\_SIGN\_OPTIONS\_WITH\_ID** Handles CORS preflight OPTIONS request for TUS resumable upload signing endpoints. Use when preparing cross-origin resumable upload requests to verify allowed methods and headers. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `wildcard` | string | ✅ | `"test-bucket/test-file.txt"` | The full path to the object for resumable upload signing, typically in format 'bucket-name/path/to/file'. This wildcard path segment is used for CORS preflight OPTIONS requests before the actual upload signing request. | *** ### `Supabase Invoke Edge Function` Integration name: **SUPABASE\_INVOKE\_EDGE\_FUNCTION** Tool to invoke a deployed Supabase Edge Function over HTTPS. Use for testing and debugging Edge Functions with configurable method, headers, body, and authentication. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `body` | — | | — | Request body to send to the function. Can be a JSON object (dict) or a raw string. | | `method` | string | | — | HTTP method to use when invoking the function. | | `headers` | object | | — | Optional additional headers to send with the request (e.g., Content-Type). | | `auth_mode` | string | | — | Authorization mode: 'anon' uses the anon key, 'service\_role' uses the service role key, 'custom\_bearer' requires a custom Authorization header in the headers parameter. | | `project_ref` | string | ✅ | `"ab12cd34ef56gh78ij90"` | Unique reference ID of the Supabase project (used in the hostname). | | `function_slug` | string | ✅ | `"hello-world"` | Name/slug of the Edge Function to invoke. | | `response_type` | string | | — | Expected response format: 'json' parses as JSON, 'text' returns raw text, 'auto' attempts JSON first then falls back to text. | *** ### `Supabase List All Organizations` Integration name: **SUPABASE\_LIST\_ALL\_ORGANIZATIONS** Lists all organizations (ID and name only) associated with the Supabase account, excluding project details within these organizations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Supabase List All Projects` Integration name: **SUPABASE\_LIST\_ALL\_PROJECTS** Retrieves a list of all Supabase projects, including their ID, name, region, and status, for the authenticated user. Authentication: - Requires a valid Bearer token in the Authorization header. - Token format: 'Bearer \' where access\_token is either: - A Personal Access Token (PAT) generated from - An OAuth2 access token with the 'Projects.Read' scope Required Scope: - Projects.Read: Allows retrieval of project metadata. Returns: List of Project objects containing id, name, organization\_id, region, status, database info, and created\_at. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Supabase List Backups` Integration name: **SUPABASE\_LIST\_BACKUPS** Lists 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | ----------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique identifier (reference string) of the Supabase project. | *** ### `Supabase List Buckets` Integration name: **SUPABASE\_LIST\_BUCKETS** Retrieves a list of all storage buckets for a Supabase project, without returning bucket contents or access policies. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | --------------------------- | ---------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-string"` | The unique identifier of the Supabase project. | *** ### `Supabase List Database Branches` Integration name: **SUPABASE\_LIST\_DATABASE\_BRANCHES** Lists all database branches for a specified Supabase project, used for isolated development and testing of schema changes; ensure the project reference ID is valid. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your_project_ref_here"` | The unique identifier (reference ID) of the Supabase project. This ID can be found in your project's dashboard URL (e.g., `https://supabase.com/dashboard/project/`). | *** ### `Supabase List Functions` Integration name: **SUPABASE\_LIST\_FUNCTIONS** Lists metadata for all Edge Functions in a Supabase project (specified by 'ref'), excluding function code or logs; the project must exist. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------- | | `ref` | string | ✅ | `"ab12cd34ef56gh78ij90"` | The unique identifier of the Supabase project. | *** ### `Supabase List Migration History` Integration name: **SUPABASE\_LIST\_MIGRATION\_HISTORY** Retrieves 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. The project must belong to the authenticated user. | *** ### `Supabase List Organization Members` Integration name: **SUPABASE\_LIST\_ORGANIZATION\_MEMBERS** Retrieves all members of a Supabase organization, identified by its unique slug, including their user ID, username, email, role, and MFA status. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------- | --------------------------------------------------------------------------- | | `slug` | string | ✅ | `"my-supabase-org"` | The unique identifier (slug) of the organization for which to list members. | *** ### `Supabase List Secrets` Integration name: **SUPABASE\_LIST\_SECRETS** Retrieves all secrets for a Supabase project using its reference ID; secret values in the response may be masked. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------------- | ---------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"projectref_0123456789abcdef"` | The unique reference ID (ref) of the Supabase project whose secrets are to be retrieved. | *** ### `Supabase List Sql Snippets` Integration name: **SUPABASE\_LIST\_SQL\_SNIPPETS** Retrieves a list of SQL snippets for the logged-in user, optionally filtered by a specific Supabase project if `project_ref` is provided. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `project_ref` | string | | — | The unique identifier for your Supabase project. It is a 20-digit string used to reference and manage your project in API endpoints. This can be found in Supabase Studio under Settings > General > Project Settings > Reference ID. | *** ### `Supabase List Sso Providers` Integration name: **SUPABASE\_LIST\_SSO\_PROVIDERS** Lists all configured Single Sign-On (SSO) providers for a Supabase project, requiring the project reference ID (`ref`) of an existing project. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | --------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-123"` | The project's reference ID. Typically found in dashboard settings or the API URL. | *** ### `Supabase List Tables` Integration name: **SUPABASE\_LIST\_TABLES** Lists all tables and views in specified database schemas, providing a quick overview of database structure to help identify available tables before fetching detailed schemas. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------------ | ------- | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `schemas` | array | | `null` | List of schemas to search for tables (maximum 10). If not provided, lists tables from all non-system schemas. Specify schema names to limit the search to specific schemas. | | `project_ref` | string | ✅ | `"huqmqtilymjtstzxbuww"` | The unique reference ID of the Supabase project. Must be exactly 20 lowercase letters (a-z only, no numbers or hyphens). This is visible in your Supabase project URL (e.g., ). | | `include_views` | boolean | | — | Whether to include views along with tables in the results | | `include_metadata` | boolean | | — | Whether to include basic metadata like estimated row count and table size | | `include_system_schemas` | boolean | | — | Whether to include system schemas (pg\_catalog, information\_schema, etc.) when listing all schemas. When set to false, temporary and internal schemas such as pg\_temp\_*, pg\_toast\_temp\_* and pgbouncer are excluded from the results. | *** ### `Supabase Patch Migration` Integration name: **SUPABASE\_PATCH\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project (used in the URL path). Must be exactly 20 lowercase letters (a-z). | | `name` | string | | `"updated_test_migration_001"` | New name for the migration entry. Updates the display name in migration history. | | `version` | string | ✅ | `"20260216042751"` | The version identifier of the migration to patch (typically a timestamp like '20260216042751'). This is found in the migration history. | | `rollback` | string | | `"DROP TABLE IF EXISTS users;"` | SQL rollback script for the migration. Defines how to revert the migration changes. | *** ### `Supabase Patch Network Restrictions` Integration name: **SUPABASE\_PATCH\_NETWORK\_RESTRICTIONS** Updates 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ---------------------------------------------------------------------- | | `add` | object | | — | Modification request for adding or removing network restriction CIDRs. | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | Unique reference ID of the Supabase project (visible in project URL). | | `remove` | object | | — | Modification request for adding or removing network restriction CIDRs. | *** ### `Supabase Push Branch` Integration name: **SUPABASE\_PUSH\_BRANCH** Pushes 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------ | :------: | ---------------------------------------- | ------------------------------------------------------------------------------------------ | | `branch_id_or_ref` | string | ✅ | `"3514a426-990d-4845-b98b-294988758cac"` | The unique identifier or reference of the database branch to push. | | `migration_version` | string | | `"20260216000000"` | Optional migration version to push to the branch. Format: timestamp like '20260216000000'. | *** ### `Supabase Reset Database Branch` Integration name: **SUPABASE\_RESET\_DATABASE\_BRANCH** Resets an existing Supabase database branch, identified by `branch_id`, to its initial clean state, irreversibly deleting all its current data and schema changes. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ------------------- | ------------------------------------------------------ | | `branch_id` | string | ✅ | `"br_123abc456def"` | The unique identifier of the database branch to reset. | *** ### `Supabase Restore Pitr Backup` Integration name: **SUPABASE\_RESTORE\_PITR\_BACKUP** Restores 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------------- | ------- | :------: | ------------------------ | -------------------------------------------------------------------- | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | Unique identifier of the Supabase project. | | `recovery_time_target_unix` | integer | ✅ | `1678886400` | Unix timestamp (seconds) for the desired database restoration point. | *** ### `Supabase Run Read Only Query` Integration name: **SUPABASE\_RUN\_READ\_ONLY\_QUERY** \[Beta] Run a SQL query as supabase\_read\_only\_user. Use when you need to safely execute SELECT queries without risk of modifying data. Only read operations are allowed. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"abcdefghijklmnopqrst"` | The unique reference ID of the Supabase project (used in the URL path). Must be exactly 20 lowercase letters (a-z). Can be found in Project Settings > General > Reference ID in the Supabase Dashboard, or from the dashboard URL: . Can also be provided as 'project\_ref'. | | `query` | string | ✅ | `"SELECT * FROM users WHERE id = 1;"` | The SQL query to be executed as supabase\_read\_only\_user. Only SELECT and other read-only operations are allowed. Write operations (INSERT, UPDATE, DELETE, CREATE, etc.) will be rejected. Can also be provided as 'sql'. IMPORTANT - Single Quote Handling: DO NOT double or escape single quotes in your SQL. The query is transmitted as a JSON string body, so standard SQL single quotes work directly. For example, write WHERE name = 'John' NOT WHERE name = ''John''. | | `parameters` | array | | `null` | Optional array of parameters for parameterized queries. Use $1, $2, etc. in the query to reference parameters. | *** ### `Supabase Select From Table` Integration name: **SUPABASE\_SELECT\_FROM\_TABLE** Tool to select rows from a Supabase/PostgREST table. Use for read-only queries with filtering, sorting, and pagination. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------- | :------: | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `limit` | integer | | `100` | Maximum number of rows to return (must be >= 1) | | `order` | string | | `"created_at.desc"` | Ordering expression in the form `column.asc` or `column.desc` | | `table` | string | ✅ | — | Table or view name to select from | | `offset` | integer | | `0` | Number of rows to skip before returning results (must be >= 0) | | `select` | string | ✅ | `"id,name"` | Comma-separated list of columns to return. Supports nested/related selections and JSON path selectors (e.g., address->postcode). | | `filters` | array | | — | Optional list of filters. Each filter will be rendered as `_=` in the query string (e.g., id\_eq=123). Can be provided as a list of FilterItem objects. Each FilterItem must have: column (string), operator (one of: eq, neq, gt, gte, lt, lte, like, ilike, is, in, cs, cd, sl, sr, nxl, nxr, adj, ov, fts, plfts, phfts, wfts), and value (the comparison value). | | `project_ref` | string | ✅ | `"ab12cd34ef56gh78ij90"` | Unique reference ID of the Supabase project (used in the hostname) | *** ### `Supabase Update A Function` Integration name: **SUPABASE\_UPDATE\_A\_FUNCTION** Updates 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. Use RETRIEVE\_A\_FUNCTION\_BODY action first to get the current source code, as this action requires sending the complete function code, not just the changes. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------- | :------: | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-example"` | The unique reference ID of the Supabase project. | | `body` | string | | `"export default async (req: Request) => { return new Response('Updated function code!'); }"` | New source code (e.g., Deno/TypeScript) or base64-encoded ESZIP content for the function, sent in the request body. | | `name` | string | | `"My Function New Name (Body)"` | Optional new name for the function. This value is sent in the request body as 'name'. | | `slug` | string | | `"my-new-function-slug"` | Optional new slug for the function. If provided as a query parameter, this changes the function's access URL. | | `import_map` | boolean | | `"true"` | Whether to use an import map for the function (query parameter). | | `verify_jwt` | boolean | | `"true"` | Specifies whether JWT verification should be enabled. This value is sent in the request body as 'verify\_jwt'. | | `function_slug` | string | ✅ | `"my-existing-function-slug"` | The current slug (unique identifier) of the Edge Function to be updated. | | `entrypoint_path` | string | | `"./functions/my-function/index.ts"` | Path to the main Deno script for the function (query parameter). | | `import_map_path` | string | | `"./functions/import_map.json"` | Path to the import map file (query parameter). | *** ### `Supabase Update Database Branch Config` Integration name: **SUPABASE\_UPDATE\_DATABASE\_BRANCH\_CONFIG** Updates the configuration of a Supabase database branch, allowing modification of its name, associated Git branch, reset-on-push behavior, persistence, and status. Note: Database branching requires a paid Supabase plan (Pro or higher). This action requires a valid branch\_id which must be exactly 20 lowercase alphabetic characters. Authentication: - Requires a valid Bearer token in the Authorization header. - Token format: 'Bearer \' Required Scope: - Environment:Write #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------- | :------: | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | | `status` | string | | `"CREATING_PROJECT"` | Status values that can be set when updating a branch. | | `branch_id` | string | ✅ | `"abcdefghijklmnopqrst"` | Unique identifier of the database branch to update. Must be exactly 20 lowercase alphabetic characters. | | `git_branch` | string | | `"main"` | Name of the Git branch to associate with this database branch. If not provided, the association remains unchanged. | | `persistent` | boolean | | `true` | If true, the database branch is persistent; non-persistent branches may be auto-cleaned. If not provided, this setting remains unchanged. | | `branch_name` | string | | `"my-feature-branch"` | New name for the database branch. If not provided, the name remains unchanged. | | `reset_on_push` | boolean | | `true` | If true, resets the database branch on new push to the linked Git branch. If not provided, this setting remains unchanged. | *** ### `Supabase Update Database Password` Integration name: **SUPABASE\_UPDATE\_DATABASE\_PASSWORD** Updates the database password for a Supabase project. Use when needing to rotate credentials or recover database access. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | ------------------------ | --------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | The unique reference ID of the Supabase project. | | `password` | string | ✅ | `"NewTestPassword123!"` | The new database password to set. Must be at least 4 characters long. | *** ### `Supabase Update Functions` Integration name: **SUPABASE\_UPDATE\_FUNCTIONS** Tool to bulk update Edge Functions in a Supabase project. Use when you need to update multiple functions at once with new configurations such as status, version, or other properties. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ------------------------ | ----------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | Supabase project reference ID. | | `functions` | array | ✅ | — | List of functions to update. Each function must have id, slug, name, status, and version. | *** ### `Supabase Update Jit Access Config` Integration name: **SUPABASE\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | Unique reference ID of the Supabase project. | | `state` | string | ✅ | `"enabled"` | Desired just-in-time access state for the project. 'enabled' activates JIT access, 'disabled' deactivates it, 'unavailable' marks the feature as unavailable. | *** ### `Supabase Update Pgsodium Config` Integration name: **SUPABASE\_UPDATE\_PGSODIUM\_CONFIG** Critically 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | --------------------------------------------------- | --------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-supabase-project-ref"` | The unique identifier (ref ID) of the Supabase project. | | `root_key` | string | ✅ | `"a-very-secure-and-randomly-generated-key-string"` | The new root encryption key for pgsodium. Must be a cryptographically strong key. | *** ### `Supabase Update Project` Integration name: **SUPABASE\_UPDATE\_PROJECT** Updates a Supabase project's configuration (currently supports updating the project name). Use when you need to rename an existing project. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | Project reference identifier (unique identifier for the project). This is typically a 20-character alphanumeric string found in your project URL or via the List All Projects endpoint. | | `name` | string | ✅ | `"my-updated-project"` | New name for the project. Must be between 1 and 256 characters. This is the human-readable display name that will appear in the Supabase dashboard. | *** ### `Supabase Update Project Auth Config` Integration name: **SUPABASE\_UPDATE\_PROJECT\_AUTH\_CONFIG** Update 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------------------------------------- | ------- | :------: | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique reference ID of the Supabase project. Can also be provided as 'project\_ref'. | | `jwt_exp` | integer | | `3600` | JWT access token expiration time in seconds. | | `site_url` | string | | `"https://example.com"` | Primary site URL used in email links and redirects. Critical for Auth redirect flows. | | `smtp_host` | string | | `"smtp.sendgrid.net"` | SMTP server host for sending auth emails. | | `smtp_pass` | string | | — | SMTP password for authentication. | | `smtp_port` | integer | | `587` | SMTP server port. | | `smtp_user` | string | | — | SMTP username for authentication. | | `disable_signup` | boolean | | — | Disable new signups via email/password and OAuth providers. | | `mailer_otp_exp` | integer | | — | Email OTP expiration time in seconds. | | `uri_allow_list` | string | | `"https://example.com/auth/callback,https://app.example.com/*"` | Comma-separated allowlist of redirect URIs/patterns for OAuth callbacks. | | `sessions_timebox` | integer | | — | Maximum session lifetime in seconds. 0 means disabled. | | `smtp_admin_email` | string | | `"noreply@example.com"` | Admin email address used as the sender for SMTP notifications. | | `smtp_sender_name` | string | | `"My App"` | Display name for the SMTP sender. | | `mailer_otp_length` | integer | | — | Email OTP length (number of digits). | | `rate_limit_verify` | integer | | — | Rate limit for verification attempts (generic). | | `external_azure_url` | string | | — | Azure OAuth issuer or discovery URL. | | `mailer_autoconfirm` | boolean | | — | Automatically confirm new signups (no email confirmation required). | | `smtp_max_frequency` | integer | | — | Rate limit for SMTP sends (emails per minute). | | `password_min_length` | integer | | `8` | Minimum required password length. | | `rate_limit_sms_sent` | integer | | — | Rate limit for sending SMS (messages per minute). | | `external_apple_secret` | string | | — | Apple OAuth client secret. | | `external_azure_secret` | string | | — | Azure OAuth client secret. | | `password_hibp_enabled` | boolean | | — | Enable HaveIBeenPwned check during password set/change. | | `rate_limit_email_sent` | integer | | — | Rate limit for sending emails (emails per minute). | | `external_apple_enabled` | boolean | | — | Enable Apple as an external OAuth provider. | | `external_azure_enabled` | boolean | | — | Enable Azure as an external OAuth provider. | | `external_email_enabled` | boolean | | — | Enable email sign-in/up. | | `external_github_secret` | string | | — | GitHub OAuth client secret. | | `external_google_secret` | string | | — | Google OAuth client secret. | | `external_phone_enabled` | boolean | | — | Enable phone (SMS) sign-in/up. | | `external_github_enabled` | boolean | | — | Enable GitHub as an external OAuth provider. | | `external_google_enabled` | boolean | | — | Enable Google as an external OAuth provider. | | `mfa_totp_enroll_enabled` | boolean | | — | Enable enrolling TOTP as an MFA factor. | | `mfa_totp_verify_enabled` | boolean | | — | Enable TOTP verification as MFA. | | `security_captcha_secret` | string | | — | CAPTCHA provider secret key. | | `external_apple_client_id` | string | | — | Apple OAuth client ID. | | `external_azure_client_id` | string | | — | Azure OAuth client ID. | | `mfa_max_enrolled_factors` | integer | | — | Maximum number of MFA factors a user can enroll. | | `security_captcha_enabled` | boolean | | — | Enable CAPTCHA verification for risky flows. | | `sessions_single_per_user` | boolean | | — | Restrict to a single active session per user. | | `external_github_client_id` | string | | — | GitHub OAuth client ID. | | `external_google_client_id` | string | | — | Google OAuth client ID. | | `security_captcha_provider` | string | | — | CAPTCHA provider (e.g., hcaptcha, turnstile). | | `rate_limit_anonymous_users` | integer | | — | Rate limit for anonymous users (requests per minute). | | `sessions_inactivity_timeout` | integer | | — | Session inactivity timeout in seconds. 0 means disabled. | | `password_required_characters` | string | | — | Character class requirements for passwords (e.g., regex or flags). | | `refresh_token_rotation_enabled` | boolean | | — | Enable refresh token rotation to reduce token replay risk. | | `security_manual_linking_enabled` | boolean | | — | Enable manual linking of identities to accounts. | | `external_anonymous_users_enabled` | boolean | | — | Enable creation of anonymous users (no credentials). | | `mailer_secure_email_change_enabled` | boolean | | — | Require secure email change flow (confirm both old and new emails). | | `security_refresh_token_reuse_interval` | integer | | — | Allowed reuse interval (seconds) for rotated refresh tokens. | | `mailer_allow_unverified_email_sign_ins` | boolean | | — | Allow sign-ins from users with unverified emails. | | `mailer_notifications_email_changed_enabled` | boolean | | — | Enable notification emails when a user's email is changed. | | `mailer_notifications_phone_changed_enabled` | boolean | | — | Enable notification emails when a phone number is changed. | | `mailer_notifications_identity_linked_enabled` | boolean | | — | Enable notification emails when an identity is linked. | | `mailer_notifications_password_changed_enabled` | boolean | | — | Enable notification emails when a password is changed. | | `mailer_notifications_identity_unlinked_enabled` | boolean | | — | Enable notification emails when an identity is unlinked. | | `mailer_notifications_mfa_factor_enrolled_enabled` | boolean | | — | Enable notification emails when an MFA factor is enrolled. | | `security_update_password_require_reauthentication` | boolean | | — | Require reauthentication before updating password. | | `mailer_notifications_mfa_factor_unenrolled_enabled` | boolean | | — | Enable notification emails when an MFA factor is unenrolled. | *** ### `Supabase Update Project Custom Hostname` Integration name: **SUPABASE\_UPDATE\_PROJECT\_CUSTOM\_HOSTNAME** Updates the custom hostname for a Supabase project, requiring subsequent DNS changes to a user-controlled domain for SSL certificate issuance and domain ownership. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------ | :------: | ---------------------- | ------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | — | The unique identifier of the Supabase project. | | `custom_hostname` | string | ✅ | `"app.yourdomain.com"` | Desired custom hostname (e.g., 'api.example.com') to associate with the project's services. | *** ### `Supabase Update Project Legacy Api Keys` Integration name: **SUPABASE\_UPDATE\_PROJECT\_LEGACY\_API\_KEYS** Tool to disable or re-enable JWT-based legacy API keys (anon, service\_role) for a Supabase project. Use when you need to toggle legacy API key access for security or migration purposes. Note: This API endpoint may be removed in the future - check for HTTP 404 Not Found if the endpoint is no longer available. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"opntiysxcrktmaarzjhz"` | The unique reference ID (20 alphanumeric characters) of your Supabase project. You can find this in your project's dashboard URL or by calling the List All Projects action. | | `enabled` | boolean | ✅ | — | Enable or disable JWT-based legacy API keys (anon, service\_role). Set to true to enable, false to disable. | *** ### `Supabase Update Project Postgres Config` Integration name: **SUPABASE\_UPDATE\_PROJECT\_POSTGRES\_CONFIG** Updates 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------------------- | ------- | :------: | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your_project_ref_123"` | The unique reference ID of the Supabase project. | | `work_mem` | string | | `"16MB"` | Memory for internal sorts and hash tables before writing to temp disk files (e.g., '4MB', '64MB'). | | `max_wal_size` | string | | `"1GB"` | WAL size that triggers a checkpoint (e.g., '1GB', '2048MB'). | | `wal_keep_size` | string | | `"256MB"` | Minimum size of past WAL log segments in pg\_wal for standby servers (e.g., '128MB', '512MB'); replaces older wal\_keep\_segments. | | `shared_buffers` | string | | `"256MB"` | Memory for shared memory buffers (e.g., '128MB', '1GB'). | | `max_connections` | integer | | `"100"` | Maximum concurrent database connections. Typically between 1 and 262143. | | `statement_timeout` | string | | `"15000ms"` | Maximum allowed duration for any SQL statement (e.g., '10000ms', '30s'); '0' typically disables timeout. | | `effective_cache_size` | string | | `"4GB"` | Estimated disk cache size for a single query (e.g., '4GB', '512MB'). | | `maintenance_work_mem` | string | | `"256MB"` | Maximum memory for maintenance operations like VACUUM, CREATE INDEX (e.g., '64MB', '1GB'). | | `max_parallel_workers` | integer | | `"4"` | Maximum workers the system can support for parallel queries. Typically between 0 and 1024. | | `max_worker_processes` | integer | | `"8"` | Maximum background processes the system can support. Typically between 0 and 262143. | | `max_slot_wal_keep_size` | string | | `"1GB"` | Maximum WAL file size replication slots can retain in pg\_wal (e.g., '1GB', '512MB'). '0' might mean unlimited; check PostgreSQL docs. | | `session_replication_role` | string | | `"origin"` | Controls firing of replication-related triggers and rules for the current session. | | `max_locks_per_transaction` | integer | | `"64"` | Controls the average number of object locks allocated per transaction. Typically between 10 and 2147483640. | | `max_standby_archive_delay` | string | | `"30s"` | Maximum delay before canceling queries on a hot standby server processing archived WAL data (e.g., '30s', '0ms' to disable). | | `max_standby_streaming_delay` | string | | `"30s"` | Maximum delay before canceling queries on a hot standby server processing streamed WAL data (e.g., '30s', '0ms' to disable). | | `max_parallel_workers_per_gather` | integer | | `"2"` | Maximum workers for a single Gather or Gather Merge node in a parallel query. Typically between 0 and 1024. | | `max_parallel_maintenance_workers` | integer | | `"2"` | Maximum parallel processes for a single maintenance utility command. Typically between 0 and 1024. | *** ### `Supabase Update Project Postgrest Config` Integration name: **SUPABASE\_UPDATE\_PROJECT\_POSTGREST\_CONFIG** Updates 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------- | :------: | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-abc123"` | The unique identifier (reference) of the Supabase project. | | `db_pool` | integer | | `"10"` | The maximum number of connections in the PostgreSQL connection pool for PostgREST. If `null` or not provided, the pool size may be automatically configured based on compute size. | | `max_rows` | integer | | `"1000"` | The maximum number of rows PostgREST can return in a single response; this setting helps control payload size and query performance. | | `db_schema` | string | | `"public"` | A comma-separated string of PostgreSQL schemas to be exposed through the PostgREST API (e.g., 'public,api'). | | `db_extra_search_path` | string | | `"utils,private"` | A comma-separated string of additional PostgreSQL schemas to search for objects if not found in the primary schema(s) defined by `db_schema`. An empty string can be used to clear existing paths. | *** ### `Supabase Update Project Supavisor Config` Integration name: **SUPABASE\_UPDATE\_PROJECT\_SUPAVISOR\_CONFIG** Updates 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------- | :------: | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref"` | The unique identifier of the Supabase project. | | `pool_mode` | string | | `"session"` | This field is deprecated and is ignored in this request. It previously controlled the pooling mode (session or transaction). | | `default_pool_size` | integer | | — | Default number of connections per user for the connection pool; helps manage concurrent database connections and performance. Optimal value depends on project's compute add-on size and workload. | *** ### `Supabase Update Ssl Enforcement Config` Integration name: **SUPABASE\_UPDATE\_SSL\_ENFORCEMENT\_CONFIG** Updates the SSL enforcement configuration (enable/disable) for a specified Supabase project's database. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------------- | ------- | :------: | -------------------- | ------------------------------------------------------------------------------------------------ | | `ref` | string | ✅ | `"your_project_ref"` | The unique identifier of the Supabase project. | | `requestedConfig__database` | boolean | | `"true"` | Desired SSL enforcement state for the project's database (`true` to enable, `false` to disable). | *** ### `Supabase Update Sso Provider` Integration name: **SUPABASE\_UPDATE\_SSO\_PROVIDER** Updates an existing SSO provider's SAML metadata, associated email domains, or attribute mappings for a Supabase project, identified by `ref` and `provider_id`. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------------- | ------ | :------: | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"ytmbklogitnlgmmszlwk"` | Unique reference ID of the Supabase project. | | `domains` | array | | `["example.com","my-company.org"]` | Email domains to associate with this SSO provider for user authentication. | | `provider_id` | string | ✅ | `"0b4b6a1e-6b2a-4b0d-869f-2edbff619583"` | UUID of the SSO provider to update. | | `metadata_url` | string | | — | URL pointing to the SAML metadata XML. Use either this or `metadata_xml`. | | `metadata_xml` | string | | — | SAML metadata XML content from the identity provider. Use either this or `metadata_url`. | | `attribute__mapping__keys` | object | | `"{'email': {'name': 'mail'}, 'full_name': {'names': ['firstName', 'lastName']}}"` | Defines mapping of SAML assertion attributes to Supabase user attributes (e.g., 'email', 'full\_name'). Values specify IdP attribute mapping using 'name', 'names' (for concatenation), or 'default'. | *** ### `Supabase Upsert Migration` Integration name: **SUPABASE\_UPSERT\_MIGRATION** Tool 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------ | :------: | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"pamqaklsszmjzugtywow"` | Project's unique reference identifier (20 lowercase letters). | | `name` | string | | `"test_migration_001"` | Optional name for the migration. Used for tracking and identification purposes. | | `query` | string | ✅ | `"CREATE TABLE IF NOT EXISTS test_table (id SERIAL PRIMARY KEY, name TEXT);"` | The SQL migration query to be stored. This query will be tracked but not executed. Must be non-empty. | | `rollback` | string | | `"DROP TABLE IF EXISTS test_table;"` | Optional rollback SQL query to undo this migration if needed. | | `idempotency_key` | string | | `"migration-2024-01-15-001"` | A unique key to ensure the same migration is tracked only once. If provided, prevents duplicate migrations with the same key. | *** ### `Supabase Verify Custom Hostname Dns` Integration name: **SUPABASE\_VERIFY\_CUSTOM\_HOSTNAME\_DNS** Re-verifies DNS and SSL configurations for an existing custom hostname associated with a Supabase project. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------- | --------------------------------------------------------------------------------------------------- | | `ref` | string | ✅ | `"your-project-ref-example"` | The unique reference ID of the Supabase project for which the custom hostname is being re-verified. | *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.toolhouse.ai/toolhouse/integrations/supabase.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.