Back to integrations

Supabase integration for background agents

Enable Supabase hosted MCP access for projects, databases, Auth, and Edge Functions.

Book a demo

Integration details

Connection

  • Hosted MCP via Supabase MCP OAuth

Agent actions

Supabase MCP

  • list_tables

    List all tables in the Supabase project database.

  • list_extensions

    List available or installed Postgres extensions.

  • list_migrations

    List database migrations.

  • apply_migration

    Apply a database migration.

  • execute_sql

    Execute SQL queries through Supabase MCP.

  • get_logs

    Retrieve service logs for API, Postgres, Edge Functions, Auth, Storage, or Realtime.

  • get_advisors

    Get security and performance advisors.

  • get_project_url

    Get the API URL for a Supabase project.

  • get_publishable_keys

    Get publishable and legacy anon API keys for a project.

  • generate_typescript_types

    Generate TypeScript types from the database schema.

  • list_edge_functions

    List all Supabase Edge Functions.

  • get_edge_function

    Get a specific Supabase Edge Function.

  • deploy_edge_function

    Deploy a Supabase Edge Function.

  • list_projects / get_project

    List or get Supabase project details.

  • create_project / pause_project / restore_project

    Manage Supabase projects.

  • list_organizations / get_organization

    Manage Supabase organization information.

  • get_cost / confirm_cost

    Review and confirm Supabase project cost information.

  • search_docs

    Search Supabase documentation.

  • create_branch / list_branches / delete_branch

    Manage Supabase branches where branching is enabled.

  • merge_branch / reset_branch / rebase_branch

    Run Supabase branch operations where branching is enabled.

  • list_storage_buckets

    List Supabase storage buckets when Storage tools are enabled.

  • get_storage_config / update_storage_config

    Read or update Supabase Storage configuration when Storage tools are enabled.

Credential safety

Credential-less sandboxes

Mistle lets agents access connected services without placing provider credentials inside the sandbox. Approved outbound requests are routed through Mistle's credential proxy, where authentication happens outside the agent runtime.

Credentials stay encrypted in Mistle's control plane and are applied only when a request is authorized for the calling sandbox and organization.

Read the credential-less sandboxes article
Diagram showing sandbox traffic routed through an egress proxy before credential injection.