other
Supabase CLI for Coding Agents
Use the Supabase CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.
9 functions 9 read 0 write Bearer token auth
Supabase CLI for Coding Agents
Let coding agents discover schemas and execute integration functions through CLI commands or MCP.
Use this pattern when another coding agent needs exact commands and schema discovery. The Supabase CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Supabase CLI for Coding Agents
kosmokrator integrations:configure supabase --set access_token="$SUPABASE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call supabase.supabase_get_current_user '{}' --json Discovery Before Execution
Agents and scripts can inspect Supabase docs and schemas before choosing a function.
kosmo integrations:docs supabase --json
kosmo integrations:docs supabase.supabase_get_current_user --json
kosmo integrations:schema supabase.supabase_get_current_user --json
kosmo integrations:search "Supabase" --json
kosmo integrations:list --json Useful Supabase CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
supabase.supabase_get_current_user | Read | none | Get the currently authenticated Supabase user profile information. |
supabase.supabase_get_project | Read | project_ref | Get details of a specific Supabase project by its reference ID. |
supabase.supabase_get_row | Read | project_ref, table_name, row_id | Get a single row from a Supabase table by its ID. |
supabase.supabase_get_settings | Read | none | Get the OpenAPI spec info for the Supabase PostgREST instance. Returns database metadata, available tables, and schema information. |
supabase.supabase_get_table | Read | project_ref, table_id | Get details of a specific table in a Supabase project by its ID. |
supabase.supabase_list_projects | Read | none | List all Supabase projects in the organization. Returns project IDs, names, and regions. |
supabase.supabase_list_rows | Read | project_ref, table_name, limit, offset, select, order | List rows in a Supabase table. Returns row data and metadata. |
supabase.supabase_list_tables | Read | project_ref | List all tables in a Supabase project. Returns table IDs, names, and schemas. |
supabase.supabase_query_with_filters | Read | table, filters_json, select, order, limit | Query a Supabase table using advanced PostgREST filter operators. Provide filters as a JSON array of objects, each with "column", "operator", and "value" keys. Supported operators: eq, neq, gt, gte, lt, lte, like, ilike, in, is, cs, cd, ov, sl, sr, nxr, nxl, adj, not, or, and. Example filters_json: [ {"column": "status", "operator": "eq", "value": "active"}, {"column": "age", "operator": "gte", "value": 18} ] |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.