How to connect Supabase to OpenClaw
Connect Supabase to OpenClaw with ClawLink in one click — 116 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
SupabaseOAUTH2MCPQuery and manage Postgres databases. Once connected, OpenClaw can read and act on Supabase from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Supabase access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Supabase setup: install one ClawHub skill, connect Supabase in the browser, and OpenClaw can call real Supabase actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Supabase skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Supabase" (hith3sh/supabase-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/supabase-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Supabase.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Supabase
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Supabase?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Supabase in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Supabase to beta run sql query and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Supabase is connected in the dashboard, that agent calls the same 116 Supabase tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Supabase MCP for OpenClaw
Looking for a Supabase MCP server for OpenClaw? ClawLink connects Supabase to OpenClaw and exposes 116 Supabase tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Supabase integration works the same way.
What the OpenClaw Supabase integration can do
116 Supabase tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 116.
30 of 116 Supabase tools for OpenClaw
| Tool | What it does |
|---|---|
Beta run SQL query supabase_beta_run_sql_query | Execute a database SQL query |
Create function supabase_create_function | Create a new Edge Function |
Deploy function supabase_deploy_function | Deploy an Edge Function |
Get function supabase_get_function | Retrieve an Edge Function |
Get health supabase_get_health | Get API health status |
Get organization supabase_get_organization | Get organization information |
Get project supabase_get_project | Get a Supabase project by ref |
Get project logs supabase_get_project_logs | Get project logs |
Get table schemas supabase_get_table_schemas | Get table schemas |
Gets project s auth config supabase_gets_project_s_auth_config | Get project's auth config |
List all organizations supabase_list_all_organizations | List all organizations |
List all projects supabase_list_all_projects | List all Supabase projects |
List backups supabase_list_backups | List project database backups |
List database branches supabase_list_database_branches | List database branches |
List functions supabase_list_functions | List all Edge Functions |
List migration history supabase_list_migration_history | List migration history |
List secrets supabase_list_secrets | List all project secrets |
List tables supabase_list_tables | List database tables |
Run read only query supabase_run_read_only_query | Execute a read-only SQL query |
Select from table supabase_select_from_table | Select rows from a table |
Alpha get third party integration supabase_alpha_get_third_party_integration | Retrieves the detailed configuration for a specific third-party authentication (TPA) provider |
Alpha list third party auth integrations supabase_alpha_list_third_party_auth_integrations | Lists all configured third-party authentication provider integrations for an existing Supabase |
Beta authorize user through oauth supabase_beta_authorize_user_through_oauth | Generates a Supabase OAuth 2.0 authorization URL for user redirection |
Beta check vanity subdomain availability supabase_beta_check_vanity_subdomain_availability | Checks if a specific vanity subdomain is available for a Supabase project; this action does not |
Beta get project custom hostname config supabase_beta_get_project_custom_hostname_config | Retrieves a Supabase project's custom hostname configuration, including its status, SSL |
Beta get project network bans supabase_beta_get_project_network_bans | Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project |
Beta get project network restrictions supabase_beta_get_project_network_restrictions | Retrieves the network restriction settings (IP allowlists) for a Supabase project |
Beta get project pgsodium config supabase_beta_get_project_pgsodium_config | Retrieves the PGSodium configuration, including the root encryption key, for an existing |
Beta get project ssl enforcement config supabase_beta_get_project_ssl_enforcement_config | Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL |
Beta get vanity subdomain config supabase_beta_get_vanity_subdomain_config | Fetches the current vanity subdomain configuration, including its status and custom domain |
Try it: find the Supabase tool you need
Browse the 30 Supabase tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Supabase to beta run sql query and walk me through the result in plain English.
Create it in Supabase for me, then confirm the important fields before you finish.
Use Supabase to deploy function and walk me through the result in plain English.
Pull the relevant data from Supabase, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Supabase working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Supabase app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Supabase through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Supabase. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Supabase actions to the runtime in a format your agent can reliably use. | 116 tools for Supabase are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Supabase to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Supabase in the browser, and the 116 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Supabase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Supabase, but the calls run through the ClawLink plugin and your connected account. Make sure Supabase is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Supabase from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Supabase tools
Supabase tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Supabase call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Supabase returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Supabase and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Supabase integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Supabase: link your Supabase account once in the browser and OpenClaw can call the Supabase API through 116 ready-made tools — no custom code or token handling.
How do I add Supabase to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Supabase skill from ClawHub, then you click Connect in the dashboard to authorize Supabase. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Supabase to OpenClaw?
About two minutes. Sign in, click Connect next to Supabase in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Supabase up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Supabase working from chat.
OpenClaw installed the Supabase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Supabase, but the calls run through the ClawLink plugin and your connected account. Make sure Supabase is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
