Latest release v2026.1001.0 is live (October 1, 2026).

See what's new

Supabase connector

Inspect tables, query data and apply migrations.

Category
Data
Tools from
Supabase
Sign-in
Choose a supported connection method
Works as
Agent tool
Source recorded

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 queryinglist_tables · execute_sql
  • Review migrations before applying onelist_migrations · apply_migration
  • Inspect functions before deployinglist_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

Supabase tools for agents32

Write 32

  • apply_migration

    Apply a database migration

  • confirm_cost

    Cost information

  • create_branch

    Branch management

  • create_project

    Manage projects

  • delete_branch

    Branch management

  • deploy_edge_function

    Deploy an Edge Function

Show all 32 Write tools
  • execute_sql

    Execute SQL queries

  • generate_typescript_types

    Generate TypeScript types from schema

  • get_advisors

    Get security and performance advisors

  • get_cost

    Cost information

  • get_edge_function

    Get a specific Edge Function

  • get_organization

    Organization management

  • get_project

    List or get project details

  • get_project_url

    Get the API URL for a project

  • get_publishable_keys

    Get publishable and legacy anon API keys for a project

  • get_storage_config

    Storage configuration

  • list_branches

    Branch management

  • list_edge_functions

    List all Edge Functions

  • list_extensions

    List available/installed Postgres extensions

  • list_migrations

    List database migrations

  • list_organizations

    Organization management

  • list_projects

    List or get project details

  • list_storage_buckets

    List storage buckets

  • list_tables

    List all tables in the database

  • merge_branch

    Branch operations

  • pause_project

    Manage projects

  • query_logs

    Run a read-only SQL query against project logs to filter, aggregate, or join across log fields.

    Full description

    Run a read-only SQL query against project logs to filter, aggregate, or join across log fields. See Query logs with SQL.

  • rebase_branch

    Branch operations

  • reset_branch

    Branch operations

  • restore_project

    Manage projects

  • search_docs

    Search Supabase documentation

  • update_storage_config

    Storage configuration

Tool availability and permissions

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.