Skip to content
Supabase logoCursor logo

Connect Supabase to Cursor

Move data between Supabase and Cursor the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Supabase triggers
1
Supabase actions
9
Cursor triggers
5
Cursor actions
4

Automation ideas

What you can build with Supabase and Cursor

A few flows teams run between Supabase and Cursor. Use one as a starting point, or build your own from scratch.

  • New Row in Supabase creates Launch Agent in Cursor

    Fires when a new row is created in a table

  • New Agent in Cursor creates Upload File in Supabase

    Triggers when a new Cursor agent is created or when agent status changes

  • New Row in Supabase creates Add Followup Instruction to Agent in Cursor

    Fires when a new row is created in a table

  • New Agent in Cursor creates Create Row in Supabase

    Triggers when a new Cursor agent is created or when agent status changes

  • New Row in Supabase creates Find Agent Status in Cursor

    Fires when a new row is created in a table

  • New Agent in Cursor creates Update Row in Supabase

    Triggers when a new Cursor agent is created or when agent status changes

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Supabase and acts in Cursor, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.