supabase-automation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Supabase Automation via Rube MCP

通过Rube MCP实现Supabase自动化

Automate Supabase operations including database queries, table schema inspection, SQL execution, project and organization management, storage buckets, edge functions, and service health monitoring through Composio's Supabase toolkit.

通过Composio的Supabase工具包，自动化Supabase的各类操作，包括数据库查询、表架构检查、SQL执行、项目与组织管理、存储桶、边缘函数及服务健康监控。

Prerequisites

前提条件

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Supabase connection via
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
supabase
```
Always call
```
RUBE_SEARCH_TOOLS
```
first to get current tool schemas

必须已连接Rube MCP（确保
```
RUBE_SEARCH_TOOLS
```
可用）
通过
```
RUBE_MANAGE_CONNECTIONS
```
使用
```
supabase
```
工具包建立有效的Supabase连接
请始终先调用
```
RUBE_SEARCH_TOOLS
```
以获取当前工具架构

Setup

配置步骤

Get Rube MCP: Add

https://rube.app/mcp

as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming
```
RUBE_SEARCH_TOOLS
```
responds
Call
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
supabase
```
If connection is not ACTIVE, follow the returned auth link to complete Supabase authentication
Confirm connection status shows ACTIVE before running any workflows

获取Rube MCP：在客户端配置中添加

https://rube.app/mcp

作为MCP服务器。无需API密钥——只需添加该端点即可使用。

通过确认
```
RUBE_SEARCH_TOOLS
```
可响应，验证Rube MCP是否可用
调用
```
RUBE_MANAGE_CONNECTIONS
```
并指定工具包为
```
supabase
```
如果连接状态不是ACTIVE，请按照返回的认证链接完成Supabase身份验证
在运行任何工作流之前，确认连接状态显示为ACTIVE

Core Workflows

核心工作流

1. Query and Manage Database Tables

1. 查询与管理数据库表

When to use: User wants to read data from tables, inspect schemas, or perform CRUD operations

Tool sequence:

```
SUPABASE_LIST_ALL_PROJECTS
```
- List projects to find the target project_ref [Prerequisite]
```
SUPABASE_LIST_TABLES
```
- List all tables and views in the database [Prerequisite]
```
SUPABASE_GET_TABLE_SCHEMAS
```
- Get detailed column types, constraints, and relationships [Prerequisite for writes]
```
SUPABASE_SELECT_FROM_TABLE
```
- Query rows with filtering, sorting, and pagination [Required for reads]
```
SUPABASE_BETA_RUN_SQL_QUERY
```
- Execute arbitrary SQL for complex queries, inserts, updates, or deletes [Required for writes]

Key parameters for SELECT_FROM_TABLE:

```
project_ref
```
: 20-character lowercase project reference
```
table
```
: Table or view name to query
```
select
```
: Comma-separated column list (supports nested selections and JSON paths like
```
profile->avatar_url
```
)
```
filters
```
: Array of filter objects with
```
column
```
,
```
operator
```
,
```
value
```
```
order
```
: Sort expression like
```
created_at.desc
```
```
limit
```
: Max rows to return (minimum 1)
```
offset
```
: Rows to skip for pagination

PostgREST filter operators:

```
eq
```
,
```
neq
```
: Equal / not equal
```
gt
```
,
```
gte
```
,
```
lt
```
,
```
lte
```
: Comparison operators
```
like
```
,
```
ilike
```
: Pattern matching (case-sensitive / insensitive)
```
is
```
: IS check (for null, true, false)
```
in
```
: In a list of values
```
cs
```
,
```
cd
```
: Contains / contained by (arrays)
```
fts
```
,
```
plfts
```
,
```
phfts
```
,
```
wfts
```
: Full-text search variants

Key parameters for RUN_SQL_QUERY:

```
ref
```
: Project reference (20 lowercase letters, pattern
```
^[a-z]{20}$
```
)
```
query
```
: Valid PostgreSQL SQL statement
```
read_only
```
: Boolean to force read-only transaction (safer for SELECTs)

Pitfalls:

```
project_ref
```
must be exactly 20 lowercase letters (a-z only, no numbers or hyphens)
```
SELECT_FROM_TABLE
```
is read-only; use
```
RUN_SQL_QUERY
```
for INSERT, UPDATE, DELETE operations
For PostgreSQL array columns (text[], integer[]), use
```
ARRAY['item1', 'item2']
```
or
```
'{"item1", "item2"}'
```
syntax, NOT JSON array syntax
```
'["item1", "item2"]'
```
SQL identifiers that are case-sensitive must be double-quoted in queries
Complex DDL operations may timeout (~60 second limit); break into smaller queries
ERROR 42P01 "relation does not exist" usually means unquoted case-sensitive identifiers
ERROR 42883 "function does not exist" means you are calling non-standard helpers; prefer information_schema queries

适用场景：用户需要从表中读取数据、检查架构或执行CRUD操作

工具执行顺序:

```
SUPABASE_LIST_ALL_PROJECTS
```
- 列出所有项目以找到目标project_ref [前置要求]
```
SUPABASE_LIST_TABLES
```
- 列出数据库中的所有表和视图 [前置要求]
```
SUPABASE_GET_TABLE_SCHEMAS
```
- 获取详细的列类型、约束及关联关系 [写入操作前置要求]
```
SUPABASE_SELECT_FROM_TABLE
```
- 带筛选、排序和分页的行查询 [读取操作必需]
```
SUPABASE_BETA_RUN_SQL_QUERY
```
- 执行任意SQL以完成复杂查询、插入、更新或删除操作 [写入操作必需]

SELECT_FROM_TABLE关键参数:

```
project_ref
```
: 20个字符的小写项目引用ID
```
table
```
: 要查询的表或视图名称
```
select
```
: 逗号分隔的列列表（支持嵌套选择和JSON路径，如
```
profile->avatar_url
```
）
```
filters
```
: 筛选对象数组，包含
```
column
```
、
```
operator
```
、
```
value
```
```
order
```
: 排序表达式，如
```
created_at.desc
```
```
limit
```
: 返回的最大行数（最小值为1）
```
offset
```
: 分页时要跳过的行数

PostgREST筛选运算符:

```
eq
```
,
```
neq
```
: 等于 / 不等于
```
gt
```
,
```
gte
```
,
```
lt
```
,
```
lte
```
: 比较运算符
```
like
```
,
```
ilike
```
: 模式匹配（区分大小写 / 不区分大小写）
```
is
```
: IS检查（用于null、true、false）
```
in
```
: 在值列表中
```
cs
```
,
```
cd
```
: 包含 / 被包含（数组类型）
```
fts
```
,
```
plfts
```
,
```
phfts
```
,
```
wfts
```
: 全文搜索变体

RUN_SQL_QUERY关键参数:

```
ref
```
: 项目引用ID（20个小写字母，格式
```
^[a-z]{20}$
```
）
```
query
```
: 有效的PostgreSQL SQL语句
```
read_only
```
: 布尔值，强制开启只读事务（对SELECT操作更安全）

注意事项:

```
project_ref
```
必须是恰好20个小写字母（仅a-z，无数字或连字符）
```
SELECT_FROM_TABLE
```
仅支持只读操作；请使用
```
RUN_SQL_QUERY
```
执行INSERT、UPDATE、DELETE操作
对于PostgreSQL数组列（text[]、integer[]），请使用
```
ARRAY['item1', 'item2']
```
或
```
'{"item1", "item2"}'
```
语法，而非JSON数组语法
```
'["item1", "item2"]'
```
区分大小写的SQL标识符在查询中必须用双引号包裹
复杂DDL操作可能超时（约60秒限制）；请拆分为更小的查询
ERROR 42P01 "relation does not exist"通常意味着未用双引号包裹区分大小写的标识符
ERROR 42883 "function does not exist"意味着你调用了非标准辅助函数；优先使用information_schema查询

2. Manage Projects and Organizations

2. 管理项目与组织

When to use: User wants to list projects, inspect configurations, or manage organizations

Tool sequence:

```
SUPABASE_LIST_ALL_ORGANIZATIONS
```
- List all organizations (IDs and names) [Required]

SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION

- Get detailed org info by slug [Optional]

```
SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION
```
- List org members with roles and MFA status [Optional]
```
SUPABASE_LIST_ALL_PROJECTS
```
- List all projects with metadata [Required]
```
SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG
```
- Get database configuration [Optional]
```
SUPABASE_GETS_PROJECT_S_AUTH_CONFIG
```
- Get authentication configuration [Optional]
```
SUPABASE_GET_PROJECT_API_KEYS
```
- Get API keys (sensitive -- handle carefully) [Optional]

SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUS

- Check service health [Optional]

Key parameters:

```
ref
```
: Project reference for project-specific tools
```
slug
```
: Organization slug (URL-friendly identifier) for org tools

services

: Array of services for health check:

auth

db

db_postgres_user

pg_bouncer

pooler

realtime

rest

storage

Pitfalls:

LIST_ALL_ORGANIZATIONS

returns both

id

and

slug

;

LIST_MEMBERS_OF_AN_ORGANIZATION

expects

slug

, not

id

```
GET_PROJECT_API_KEYS
```
returns live secrets -- NEVER log, display, or persist full key values
```
GETS_PROJECT_S_SERVICE_HEALTH_STATUS
```
requires a non-empty
```
services
```
array; empty array causes invalid_request error
Config tools may return 401/403 if token lacks required scope; handle gracefully rather than failing the whole workflow

适用场景：用户需要列出项目、检查配置或管理组织

工具执行顺序:

```
SUPABASE_LIST_ALL_ORGANIZATIONS
```
- 列出所有组织（ID和名称）[必需]

SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION

- 通过slug获取组织详细信息 [可选]

```
SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION
```
- 列出组织成员及其角色和MFA状态 [可选]
```
SUPABASE_LIST_ALL_PROJECTS
```
- 列出所有项目及其元数据 [必需]
```
SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG
```
- 获取数据库配置 [可选]
```
SUPABASE_GETS_PROJECT_S_AUTH_CONFIG
```
- 获取身份验证配置 [可选]
```
SUPABASE_GET_PROJECT_API_KEYS
```
- 获取API密钥（敏感信息——请谨慎处理）[可选]

SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUS

- 检查服务健康状态 [可选]

关键参数:

```
ref
```
: 项目特定工具所需的项目引用ID
```
slug
```
: 组织工具所需的组织slug（URL友好标识符）

services

: 健康检查的服务数组：

auth

、

db

、

db_postgres_user

、

pg_bouncer

、

pooler

、

realtime

、

rest

、

storage

注意事项:

LIST_ALL_ORGANIZATIONS

会返回

id

和

slug

；

LIST_MEMBERS_OF_AN_ORGANIZATION

需要的是

slug

而非

id

```
GET_PROJECT_API_KEYS
```
返回的是可用的密钥——切勿记录、显示或持久化完整密钥值
```
GETS_PROJECT_S_SERVICE_HEALTH_STATUS
```
需要非空的
```
services
```
数组；空数组会导致invalid_request错误
如果令牌缺少必要的权限范围，配置工具可能返回401/403错误；请优雅处理而非终止整个工作流

3. Inspect Database Schema

3. 检查数据库架构

When to use: User wants to understand table structure, columns, constraints, or generate types

Tool sequence:

```
SUPABASE_LIST_ALL_PROJECTS
```
- Find the target project [Prerequisite]
```
SUPABASE_LIST_TABLES
```
- Enumerate all tables and views with metadata [Required]
```
SUPABASE_GET_TABLE_SCHEMAS
```
- Get detailed schema for specific tables [Required]
```
SUPABASE_GENERATE_TYPE_SCRIPT_TYPES
```
- Generate TypeScript types from schema [Optional]

Key parameters for LIST_TABLES:

```
project_ref
```
: Project reference
```
schemas
```
: Array of schema names to search (e.g.,
```
["public"]
```
); omit for all non-system schemas
```
include_views
```
: Include views alongside tables (default true)
```
include_metadata
```
: Include row count estimates and sizes (default true)
```
include_system_schemas
```
: Include pg_catalog, information_schema, etc. (default false)

Key parameters for GET_TABLE_SCHEMAS:

```
project_ref
```
: Project reference
```
table_names
```
: Array of table names (max 20 per request); supports schema prefix like
```
public.users
```
,
```
auth.users
```
```
include_relationships
```
: Include foreign key info (default true)
```
include_indexes
```
: Include index info (default true)
```
exclude_null_values
```
: Cleaner output by hiding null fields (default true)

Key parameters for GENERATE_TYPE_SCRIPT_TYPES:

```
ref
```
: Project reference
```
included_schemas
```
: Comma-separated schema names (default
```
"public"
```
)

Pitfalls:

Table names without schema prefix assume
```
public
```
schema
```
row_count
```
and
```
size_bytes
```
from LIST_TABLES may be null for views or recently created tables; treat as unknown, not zero
GET_TABLE_SCHEMAS has a max of 20 tables per request; batch if needed
TypeScript types include all tables in specified schemas; cannot filter individual tables

适用场景：用户需要了解表结构、列、约束或生成类型定义

工具执行顺序:

```
SUPABASE_LIST_ALL_PROJECTS
```
- 找到目标项目 [前置要求]
```
SUPABASE_LIST_TABLES
```
- 枚举所有表和视图及其元数据 [必需]
```
SUPABASE_GET_TABLE_SCHEMAS
```
- 获取特定表的详细架构 [必需]
```
SUPABASE_GENERATE_TYPE_SCRIPT_TYPES
```
- 从架构生成TypeScript类型 [可选]

LIST_TABLES关键参数:

```
project_ref
```
: 项目引用ID
```
schemas
```
: 要搜索的架构名称数组（例如
```
["public"]
```
）；留空则包含所有非系统架构
```
include_views
```
: 包含视图（默认true）
```
include_metadata
```
: 包含行计数估算和大小（默认true）
```
include_system_schemas
```
: 包含pg_catalog、information_schema等系统架构（默认false）

GET_TABLE_SCHEMAS关键参数:

```
project_ref
```
: 项目引用ID
```
table_names
```
: 表名称数组（每次请求最多20个）；支持架构前缀，如
```
public.users
```
、
```
auth.users
```
```
include_relationships
```
: 包含外键信息（默认true）
```
include_indexes
```
: 包含索引信息（默认true）
```
exclude_null_values
```
: 隐藏空字段以简化输出（默认true）

GENERATE_TYPE_SCRIPT_TYPES关键参数:

```
ref
```
: 项目引用ID
```
included_schemas
```
: 逗号分隔的架构名称（默认
```
"public"
```
）

注意事项:

不带架构前缀的表名称默认使用
```
public
```
架构
```
LIST_TABLES
```
返回的
```
row_count
```
和
```
size_bytes
```
对于视图或新建表可能为null；请视为未知值而非0
```
GET_TABLE_SCHEMAS
```
每次请求最多支持20个表；如有需要请分批处理
TypeScript类型会包含指定架构中的所有表；无法过滤单个表

4. Manage Edge Functions

4. 管理边缘函数

When to use: User wants to list, inspect, or work with Supabase Edge Functions

Tool sequence:

```
SUPABASE_LIST_ALL_PROJECTS
```
- Find the project reference [Prerequisite]
```
SUPABASE_LIST_ALL_FUNCTIONS
```
- List all edge functions with metadata [Required]
```
SUPABASE_RETRIEVE_A_FUNCTION
```
- Get detailed info for a specific function [Optional]

Key parameters:

```
ref
```
: Project reference
Function slug for RETRIEVE_A_FUNCTION

Pitfalls:

```
LIST_ALL_FUNCTIONS
```
returns metadata only, not function code or logs
```
created_at
```
and
```
updated_at
```
may be epoch milliseconds; convert to human-readable timestamps
These tools cannot create or deploy edge functions; they are read-only inspection tools
Permission errors may occur without org/project admin rights

适用场景：用户需要列出、检查Supabase边缘函数

工具执行顺序:

```
SUPABASE_LIST_ALL_PROJECTS
```
- 找到项目引用ID [前置要求]
```
SUPABASE_LIST_ALL_FUNCTIONS
```
- 列出所有边缘函数及其元数据 [必需]
```
SUPABASE_RETRIEVE_A_FUNCTION
```
- 获取特定函数的详细信息 [可选]

关键参数:

```
ref
```
: 项目引用ID
RETRIEVE_A_FUNCTION所需的函数slug

注意事项:

```
LIST_ALL_FUNCTIONS
```
仅返回元数据，不包含函数代码或日志
```
created_at
```
和
```
updated_at
```
可能为毫秒级时间戳；请转换为人类可读的时间格式
这些工具无法创建或部署边缘函数；仅支持只读检查
若无组织/项目管理员权限，可能会出现权限错误

5. Manage Storage Buckets

5. 管理存储桶

When to use: User wants to list storage buckets or manage file storage

Tool sequence:

```
SUPABASE_LIST_ALL_PROJECTS
```
- Find the project reference [Prerequisite]
```
SUPABASE_LISTS_ALL_BUCKETS
```
- List all storage buckets [Required]

Key parameters:

```
ref
```
: Project reference

Pitfalls:

```
LISTS_ALL_BUCKETS
```
returns bucket list only, not bucket contents or access policies
For file uploads,
```
SUPABASE_RESUMABLE_UPLOAD_SIGN_OPTIONS_WITH_ID
```
handles CORS preflight for TUS resumable uploads only
Direct file operations may require using
```
proxy_execute
```
with the Supabase storage API

适用场景：用户需要列出存储桶或管理文件存储

工具执行顺序:

```
SUPABASE_LIST_ALL_PROJECTS
```
- 找到项目引用ID [前置要求]
```
SUPABASE_LISTS_ALL_BUCKETS
```
- 列出所有存储桶 [必需]

关键参数:

```
ref
```
: 项目引用ID

注意事项:

```
LISTS_ALL_BUCKETS
```
仅返回存储桶列表，不包含桶内容或访问策略
对于文件上传，
```
SUPABASE_RESUMABLE_UPLOAD_SIGN_OPTIONS_WITH_ID
```
仅处理TUS可恢复上传的CORS预检
直接文件操作可能需要结合Supabase存储API使用
```
proxy_execute
```

Common Patterns

通用模式

ID Resolution

ID解析

Project reference:
```
SUPABASE_LIST_ALL_PROJECTS
```
-- extract
```
ref
```
field (20 lowercase letters)
Organization slug:
```
SUPABASE_LIST_ALL_ORGANIZATIONS
```
-- use
```
slug
```
(not
```
id
```
) for downstream org tools
Table names:
```
SUPABASE_LIST_TABLES
```
-- enumerate available tables before querying
Schema discovery:
```
SUPABASE_GET_TABLE_SCHEMAS
```
-- inspect columns and constraints before writes

项目引用ID: 通过
```
SUPABASE_LIST_ALL_PROJECTS
```
提取
```
ref
```
字段（20个小写字母）
组织slug: 通过
```
SUPABASE_LIST_ALL_ORGANIZATIONS
```
获取
```
slug
```
（而非
```
id
```
）以用于后续组织工具
表名称: 通过
```
SUPABASE_LIST_TABLES
```
枚举可用表后再进行查询
架构发现: 通过
```
SUPABASE_GET_TABLE_SCHEMAS
```
在写入操作前检查列和约束

Pagination

分页

```
SUPABASE_SELECT_FROM_TABLE
```
: Uses
```
offset
```
+
```
limit
```
pagination. Increment offset by limit until fewer rows than limit are returned.
```
SUPABASE_LIST_ALL_PROJECTS
```
: May paginate for large accounts; follow cursors/pages until exhausted.
```
SUPABASE_LIST_TABLES
```
: May paginate for large databases.

```
SUPABASE_SELECT_FROM_TABLE
```
: 使用
```
offset
```
+
```
limit
```
分页。将offset按limit递增，直到返回的行数少于limit
```
SUPABASE_LIST_ALL_PROJECTS
```
: 对于大型账户可能会分页；请跟随游标/页面直到获取全部数据
```
SUPABASE_LIST_TABLES
```
: 对于大型数据库可能会分页

SQL Best Practices

SQL最佳实践

Always use

SUPABASE_GET_TABLE_SCHEMAS

SUPABASE_LIST_TABLES

before writing SQL

Use
```
read_only: true
```
for SELECT queries to prevent accidental mutations

Quote case-sensitive identifiers:

SELECT * FROM "MyTable"

not

SELECT * FROM MyTable

Use PostgreSQL array syntax for array columns:
```
ARRAY['a', 'b']
```
not
```
['a', 'b']
```
Break complex DDL into smaller statements to avoid timeouts

编写SQL前请务必使用

SUPABASE_GET_TABLE_SCHEMAS

或

SUPABASE_LIST_TABLES

对于SELECT查询，请使用
```
read_only: true
```
以防止意外修改
区分大小写的标识符请加双引号：
```
SELECT * FROM "MyTable"
```
而非
```
SELECT * FROM MyTable
```
数组列请使用PostgreSQL数组语法：
```
ARRAY['a', 'b']
```
而非
```
['a', 'b']
```
将复杂DDL拆分为更小的语句以避免超时

Known Pitfalls

已知注意事项

ID Formats

ID格式

Project references are exactly 20 lowercase letters (a-z): pattern
```
^[a-z]{20}$
```
Organization identifiers come as both
```
id
```
(UUID) and
```
slug
```
(URL-friendly string); tools vary in which they accept
```
LIST_MEMBERS_OF_AN_ORGANIZATION
```
requires
```
slug
```
, not
```
id
```

项目引用ID必须是恰好20个小写字母（a-z）：格式
```
^[a-z]{20}$
```
组织标识符包含
```
id
```
（UUID）和
```
slug
```
（URL友好字符串）；不同工具对其要求不同
```
LIST_MEMBERS_OF_AN_ORGANIZATION
```
需要的是
```
slug
```
而非
```
id
```

SQL Execution

SQL执行

```
BETA_RUN_SQL_QUERY
```
has ~60 second timeout for complex operations
PostgreSQL array syntax required:
```
ARRAY['item']
```
or
```
'{"item"}'
```
, NOT JSON syntax
```
'["item"]'
```
Case-sensitive identifiers must be double-quoted in SQL
ERROR 42P01: relation does not exist (check quoting and schema prefix)
ERROR 42883: function does not exist (use information_schema instead of custom helpers)

```
BETA_RUN_SQL_QUERY
```
对复杂操作有约60秒的超时限制
必须使用PostgreSQL数组语法：
```
ARRAY['item']
```
或
```
'{"item"}'
```
，而非JSON语法
```
'["item"]'
```
区分大小写的标识符在SQL中必须用双引号包裹
ERROR 42P01: relation does not exist（检查引号和架构前缀）
ERROR 42883: function does not exist（使用information_schema而非自定义辅助函数）

Sensitive Data

敏感数据

```
GET_PROJECT_API_KEYS
```
returns service-role keys -- NEVER expose full values
Auth config tools exclude secrets but may still contain sensitive configuration
Always mask or truncate API keys in output

```
GET_PROJECT_API_KEYS
```
返回服务角色密钥——切勿暴露完整密钥值
身份验证配置工具会排除密钥，但仍可能包含敏感配置信息
在输出中请始终掩码或截断API密钥

Schema Metadata

架构元数据

```
row_count
```
and
```
size_bytes
```
from
```
LIST_TABLES
```
can be null; do not treat as zero
System schemas are excluded by default; set
```
include_system_schemas: true
```
to see them
Views appear alongside tables unless
```
include_views: false
```

```
LIST_TABLES
```
返回的
```
row_count
```
和
```
size_bytes
```
可能为null；请勿视为0
默认排除系统架构；设置
```
include_system_schemas: true
```
以查看
除非设置
```
include_views: false
```
，否则视图会与表一同显示

Rate Limits and Permissions

速率限制与权限

Enrichment tools (API keys, configs) may return 401/403 without proper scopes; skip gracefully
Large table listings may require pagination
```
GETS_PROJECT_S_SERVICE_HEALTH_STATUS
```
fails with empty
```
services
```
array -- always specify at least one

增强工具（如API密钥、配置）若无足够权限范围可能返回401/403错误；请优雅跳过而非终止
大型表列表可能需要分页
```
GETS_PROJECT_S_SERVICE_HEALTH_STATUS
```
在
```
services
```
数组为空时会失败——请始终至少指定一个服务

Quick Reference

快速参考

Task	Tool Slug	Key Params
List organizations	`SUPABASE_LIST_ALL_ORGANIZATIONS`	(none)
Get org info	`SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION`	`slug`
List org members	`SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION`	`slug`
List projects	`SUPABASE_LIST_ALL_PROJECTS`	(none)
List tables	`SUPABASE_LIST_TABLES`	`project_ref` , `schemas`
Get table schemas	`SUPABASE_GET_TABLE_SCHEMAS`	`project_ref` , `table_names`
Query table	`SUPABASE_SELECT_FROM_TABLE`	`project_ref` , `table` , `select` , `filters`
Run SQL	`SUPABASE_BETA_RUN_SQL_QUERY`	`ref` , `query` , `read_only`
Generate TS types	`SUPABASE_GENERATE_TYPE_SCRIPT_TYPES`	`ref` , `included_schemas`
Postgres config	`SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG`	`ref`
Auth config	`SUPABASE_GETS_PROJECT_S_AUTH_CONFIG`	`ref`
Get API keys	`SUPABASE_GET_PROJECT_API_KEYS`	`ref`
Service health	`SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUS`	`ref` , `services`
List edge functions	`SUPABASE_LIST_ALL_FUNCTIONS`	`ref`
Get edge function	`SUPABASE_RETRIEVE_A_FUNCTION`	`ref` , function slug
List storage buckets	`SUPABASE_LISTS_ALL_BUCKETS`	`ref`
List DB branches	`SUPABASE_LIST_ALL_DATABASE_BRANCHES`	`ref`

任务	工具Slug	关键参数
列出组织	`SUPABASE_LIST_ALL_ORGANIZATIONS`	无
获取组织信息	`SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION`	`slug`
列出组织成员	`SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION`	`slug`
列出项目	`SUPABASE_LIST_ALL_PROJECTS`	无
列出表	`SUPABASE_LIST_TABLES`	`project_ref` , `schemas`
获取表架构	`SUPABASE_GET_TABLE_SCHEMAS`	`project_ref` , `table_names`
查询表	`SUPABASE_SELECT_FROM_TABLE`	`project_ref` , `table` , `select` , `filters`
执行SQL	`SUPABASE_BETA_RUN_SQL_QUERY`	`ref` , `query` , `read_only`
生成TS类型	`SUPABASE_GENERATE_TYPE_SCRIPT_TYPES`	`ref` , `included_schemas`
Postgres配置	`SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG`	`ref`
身份验证配置	`SUPABASE_GETS_PROJECT_S_AUTH_CONFIG`	`ref`
获取API密钥	`SUPABASE_GET_PROJECT_API_KEYS`	`ref`
服务健康状态	`SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUS`	`ref` , `services`
列出边缘函数	`SUPABASE_LIST_ALL_FUNCTIONS`	`ref`
获取边缘函数	`SUPABASE_RETRIEVE_A_FUNCTION`	`ref` , function slug
列出存储桶	`SUPABASE_LISTS_ALL_BUCKETS`	`ref`
列出数据库分支	`SUPABASE_LIST_ALL_DATABASE_BRANCHES`	`ref`