> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchhive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supabase

> Give an agent access to your connected Supabase account so it can query data and manage projects

Supabase gives your agent access to your connected organization account. The agent can list projects, query tables, run SQL, retrieve database metadata, and manage Edge Functions while it responds to chat messages or completes tasks.

## What it does

When Supabase is enabled on an agent, the agent can automatically perform Supabase actions as part of its reasoning process. You ask a question or give it a task — the agent decides when and how to use your Supabase account on your behalf.

## Prerequisites

You must have an active Supabase connection in your workspace before enabling this tool. If no active connection exists, the toggle is disabled.

1. Go to **Integrations** for your workspace.
2. Find **Supabase** in the integrations grid.
3. Click **Connect** and complete the OAuth flow.
4. Return to your agent and enable the tool.

## Adding the tool to an agent

1. Open an agent in the editor.
2. Click the button with the tooltip **Add MCP Tool or Sub Agent**.
3. In **MCP Tools**, click **Supabase**. The Supabase node appears on the canvas.
4. Click the node to open the **Settings** panel on the right.
5. In the **Authentication** field, select the connected Supabase account the agent should use.
6. If no active connection is found, the settings panel shows a warning with a link to **Integrations** to connect first.

## Use cases

* Query a Supabase table to answer questions about your application data.
* Run read-only SQL to investigate records or generate reports in chat.
* List projects and retrieve database schema metadata before drafting migrations.
* Deploy or update Edge Functions after generating code in a conversation.

## Notes

* The agent uses your connected Supabase account to perform actions. Connect an organization account with the permissions your use cases require.
* Agents have access to all non-destructive Supabase tools, including write-capable SQL queries and migration actions. Destructive actions (delete, remove, revoke) are blocked.
* Supabase is not available when the agent model provider is Google/Gemini.
* This tool counts as 1 credit per action the agent performs.
* OAuth may show third-party authorization branding during the connect flow.

See also: [Integrations](../../workspace/integrations), [Creating and Configuring](../creating-and-configuring)