Skip to content
Azure DevOps logoCursor logo

Connect Azure DevOps to Cursor

Move data between Azure DevOps 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.

Azure DevOps triggers
2
Azure DevOps actions
6
Cursor triggers
5
Cursor actions
4

Automation ideas

What you can build with Azure DevOps and Cursor

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

  • New or Updated Work Item (Instant) in Azure DevOps creates Launch Agent in Cursor

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Agent in Cursor creates Create Work Item in Azure DevOps

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

  • New or Updated Work Item (Instant) in Azure DevOps creates Add Followup Instruction to Agent in Cursor

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Agent in Cursor creates Get Work Item in Azure DevOps

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

  • New or Updated Work Item (Instant) in Azure DevOps creates Find Agent Status in Cursor

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Agent in Cursor creates Update Work Item in Azure DevOps

    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 Azure DevOps 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.