Kiwi
Kiwi

Kiwi for Supabase

Have the agent on a Kiwi step apply a database migration to a Supabase project and run the advisors afterwards, through Supabase's MCP server.

  • Your agent works in Supabase through its own connection. Kiwi does not call Supabase and never holds its credentials.
  • A workflow skill can list Supabase among the tools it requires. When you supply your agent's available tools to a skill check and Supabase is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Supabase, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Supabase connection, with report_configuration.
  • The agent submits links to its work in Supabase as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Supabase

  • List tables and migrations, and apply a new migration.
  • Run SQL, or connect in read-only mode so that every query runs as a read-only Postgres user.
  • Read project logs and the security and performance advisors.
  • Generate TypeScript types from the database schema.
  • List and deploy Edge Functions.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

    Coding agentsQuickstart

  2. Connect your agent to Supabase

    Add the Supabase MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.supabase.com/mcp

    Supabase documentation

  3. Example skill

    Publish instructions like these as a workflow skill that lists Supabase among its required tools.

    Read the migration file and the development project ref from the inputs.
Apply the migration to that project through Supabase, then run the
security and performance advisors.
Generate TypeScript types and commit them with the migration.
Submit the advisor results and the commit link as the step's outputs.
Applying it to the production project is a decision for the run's Owner.
If the migration fails, report a blocker with the error.
Get startedRead the setup guide