# Supabase connector

[Product](https://paperclip.ing/product/) / [Connectors](https://paperclip.ing/product/connectors/) / Supabase

Inspect tables, query data and apply migrations.

Category: [Data](/product/connectors/?category=data)
Tools from: [Supabase](https://supabase.com/docs/guides/ai-tools/mcp)
Sign-in: Choose a supported connection method
Works as: Agent tool

Source recorded: Sep 30, 2026

## Overview

Paperclip’s Supabase MCP connector gives your AI agents tools to inspect tables, query data and apply migrations. Each tool can be Allowed, Ask first or Off.

The account’s Supabase permissions are narrowed to the required project reference. Supabase enforces the requested read-only and feature-group parameters.

## What agents can do with Supabase

- Inspect tables before querying (`list_tables`, `execute_sql`)
- Review migrations before applying one (`list_migrations`, `apply_migration`)
- Inspect functions before deploying (`list_edge_functions`, `deploy_edge_function`)

## How to connect Supabase

1. In Paperclip, open Connectors and select Supabase.
2. On the Access step, choose the identity and which agents may use the connection.
3. Select Sign in with Supabase or Use an API key with a personal access token. Enter the required project reference and choose read-only mode and feature groups before finishing.

[Setup guide](https://docs.paperclip.ing/connectors/supabase/)

## Supabase tools for agents (32)



### Write (32)

<div data-tool-name="apply_migration" data-tool-class="write">
<code>apply_migration</code>
<p class="c4-description-summary">Apply a database migration</p>
</div>

<div data-tool-name="confirm_cost" data-tool-class="write">
<code>confirm_cost</code>
<p class="c4-description-summary">Cost information</p>
</div>

<div data-tool-name="create_branch" data-tool-class="write">
<code>create_branch</code>
<p class="c4-description-summary">Branch management</p>
</div>

<div data-tool-name="create_project" data-tool-class="write">
<code>create_project</code>
<p class="c4-description-summary">Manage projects</p>
</div>

<div data-tool-name="delete_branch" data-tool-class="write">
<code>delete_branch</code>
<p class="c4-description-summary">Branch management</p>
</div>

<div data-tool-name="deploy_edge_function" data-tool-class="write">
<code>deploy_edge_function</code>
<p class="c4-description-summary">Deploy an Edge Function</p>
</div>

<div data-tool-name="execute_sql" data-tool-class="write">
<code>execute_sql</code>
<p class="c4-description-summary">Execute SQL queries</p>
</div>

<div data-tool-name="generate_typescript_types" data-tool-class="write">
<code>generate_typescript_types</code>
<p class="c4-description-summary">Generate TypeScript types from schema</p>
</div>

<div data-tool-name="get_advisors" data-tool-class="write">
<code>get_advisors</code>
<p class="c4-description-summary">Get security and performance advisors</p>
</div>

<div data-tool-name="get_cost" data-tool-class="write">
<code>get_cost</code>
<p class="c4-description-summary">Cost information</p>
</div>

<div data-tool-name="get_edge_function" data-tool-class="write">
<code>get_edge_function</code>
<p class="c4-description-summary">Get a specific Edge Function</p>
</div>

<div data-tool-name="get_organization" data-tool-class="write">
<code>get_organization</code>
<p class="c4-description-summary">Organization management</p>
</div>

<div data-tool-name="get_project" data-tool-class="write">
<code>get_project</code>
<p class="c4-description-summary">List or get project details</p>
</div>

<div data-tool-name="get_project_url" data-tool-class="write">
<code>get_project_url</code>
<p class="c4-description-summary">Get the API URL for a project</p>
</div>

<div data-tool-name="get_publishable_keys" data-tool-class="write">
<code>get_publishable_keys</code>
<p class="c4-description-summary">Get publishable and legacy anon API keys for a project</p>
</div>

<div data-tool-name="get_storage_config" data-tool-class="write">
<code>get_storage_config</code>
<p class="c4-description-summary">Storage configuration</p>
</div>

<div data-tool-name="list_branches" data-tool-class="write">
<code>list_branches</code>
<p class="c4-description-summary">Branch management</p>
</div>

<div data-tool-name="list_edge_functions" data-tool-class="write">
<code>list_edge_functions</code>
<p class="c4-description-summary">List all Edge Functions</p>
</div>

<div data-tool-name="list_extensions" data-tool-class="write">
<code>list_extensions</code>
<p class="c4-description-summary">List available/installed Postgres extensions</p>
</div>

<div data-tool-name="list_migrations" data-tool-class="write">
<code>list_migrations</code>
<p class="c4-description-summary">List database migrations</p>
</div>

<div data-tool-name="list_organizations" data-tool-class="write">
<code>list_organizations</code>
<p class="c4-description-summary">Organization management</p>
</div>

<div data-tool-name="list_projects" data-tool-class="write">
<code>list_projects</code>
<p class="c4-description-summary">List or get project details</p>
</div>

<div data-tool-name="list_storage_buckets" data-tool-class="write">
<code>list_storage_buckets</code>
<p class="c4-description-summary">List storage buckets</p>
</div>

<div data-tool-name="list_tables" data-tool-class="write">
<code>list_tables</code>
<p class="c4-description-summary">List all tables in the database</p>
</div>

<div data-tool-name="merge_branch" data-tool-class="write">
<code>merge_branch</code>
<p class="c4-description-summary">Branch operations</p>
</div>

<div data-tool-name="pause_project" data-tool-class="write">
<code>pause_project</code>
<p class="c4-description-summary">Manage projects</p>
</div>

<div data-tool-name="query_logs" data-tool-class="write">
<code>query_logs</code>
<p class="c4-description-summary">Run a read-only SQL query against project logs to filter, aggregate, or join across log fields.</p>
<details class="faq-item c4-tool-description">
<summary class="faq-header" aria-label="Full description for query_logs">Full description</summary>

<pre class="faq-answer c4-description-text">Run a read-only SQL query against project logs to filter, aggregate, or join across log fields. See Query logs with SQL.</pre>
</details>
</div>

<div data-tool-name="rebase_branch" data-tool-class="write">
<code>rebase_branch</code>
<p class="c4-description-summary">Branch operations</p>
</div>

<div data-tool-name="reset_branch" data-tool-class="write">
<code>reset_branch</code>
<p class="c4-description-summary">Branch operations</p>
</div>

<div data-tool-name="restore_project" data-tool-class="write">
<code>restore_project</code>
<p class="c4-description-summary">Manage projects</p>
</div>

<div data-tool-name="search_docs" data-tool-class="write">
<code>search_docs</code>
<p class="c4-description-summary">Search Supabase documentation</p>
</div>

<div data-tool-name="update_storage_config" data-tool-class="write">
<code>update_storage_config</code>
<p class="c4-description-summary">Storage configuration</p>
</div>

This list describes the reviewed tools. Your selected method, provider access and action permissions determine what agents can use.

These lists use a conservative permission policy. Read requires a provider read-only hint or a reviewed Paperclip read rule. Evidence that an action changes data or submits information elsewhere puts it in Write. Write also includes actions we cannot verify as read-only. Read describes the reviewed evidence; it does not guarantee that an action has no side effects. A connected account can group actions differently.

This list includes experimental branching tools and storage tools that are Off by default. Project scope, read-only mode and feature selection can limit availability. The list does not establish account access.



### Connection policies

Discovered actions follow the connection’s policies. Review their permissions and set actions to Ask first or Off as needed. Read-only mode is off by default; turn it on before connecting to limit database and schema changes.

## Supabase connector FAQ

### Can I require approval for actions?

Set an action to Ask first to require human approval of each call or Off to prevent calls. Allowed actions run without approval. Read and Write grouping is separate from these settings.

### What can agents reach in Supabase?

The account’s Supabase permissions are narrowed to the required project reference. Supabase enforces the requested read-only and feature-group parameters.

### What do I need before connecting?

Use a development project and its project reference. The key method takes a personal access token, not a project anon or service-role key.


Ways to connect

- Sign in with Supabase
  - Use browser sign-in for the provider-hosted server.
- Use an API key
  - Use your own restricted key when browser sign-in is not suitable.

[Supabase connector](https://docs.paperclip.ing/connectors/supabase/)

[Set action permissions](https://docs.paperclip.ing/connectors/action-permissions/)

## Related connectors

- [Airtable](https://paperclip.ing/product/connectors/airtable/): Find records, inspect fields and update table rows.
- [ClickHouse](https://paperclip.ing/product/connectors/clickhouse/): Connect a ClickHouse Cloud ClickStack service.
- [Google Sheets](https://paperclip.ing/product/connectors/google-sheets/): Read spreadsheets and update values and formulas.

## Give your agents Supabase.

Join the Paperclip waitlist to connect Supabase and choose what your agents can do.

[Join the waitlist](https://paperclip.ing/waitlist/)