--- title: "Connect Azure Service Bus and Cursor - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Add Followup Instruction to Agent\" in Cursor." canonical: "https://apiant.ai/connect/azure-service-bus-to-cursor" --- # Connect Azure Service Bus and Cursor When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Add Followup Instruction to Agent** in [Cursor](https://apiant.ai/connections/cursor), or **Agent Pull Request Created** in Cursor to **Send Message to Queue** in Azure Service Bus. Describe the whole flow and it is built, tested on every scenario and kept running. Azure Service Bus **1** trigger Azure Service Bus **9** actions Cursor **3** triggers Cursor **11** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Azure Service Bus and Cursor to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Azure Service Bus and Cursor can do together ### From Azure Service Bus to Cursor - When **New Message in Queue** in Azure Service Bus then **Add Followup Instruction to Agent** in Cursor - When **New Message in Queue** in Azure Service Bus then **Launch Agent** in Cursor ### From Cursor to Azure Service Bus - When **Agent Pull Request Created** in Cursor then **Send Message to Queue** in Azure Service Bus - When **New Agent** in Cursor then **Abandon Message** in Azure Service Bus Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Azure Service Bus and Cursor ## Triggers and actions 4 triggers · 20 actions - Trigger **New Message in Queue** Triggers when a message arrives in a Service Bus queue. Each check picks up the next message and removes it from the queue, so use a queue dedicated to this automation. - Action **Abandon Message** Abandons a message received with Receive Message (Peek-Lock), releasing its lock so it can be received again. - Action **Complete Message** Completes a message received with Receive Message (Peek-Lock), removing it from the queue. - Action **Create Queue** Creates a new queue in the connected Service Bus namespace and returns its settings. - Action **Delete Queue** Deletes a queue from the connected Service Bus namespace, along with all of its messages. - Action **Get Queue** Returns a Service Bus queue's settings and its current message counts. - Action **List Queues** Returns the queues in the connected Service Bus namespace, with each queue's status and message counts. - Action **Receive and Delete Message** Receives the next message from a queue in the connected Service Bus namespace and removes it from the queue. - Action **Receive Message (Peek-Lock)** Receives the next message from a queue and locks it, so another receiver cannot take it. Complete the message to remove it, or abandon it to release it back to the queue; the lock expires on its own after the queue's lock duration. - Action **Send Message to Queue** Sends a message to a queue in the connected Service Bus namespace, with optional subject, IDs, scheduling and custom properties. - Trigger **Agent Pull Request Created** Triggers when the selected Cursor cloud agent opens a new GitHub pull request. - Trigger **Agent Status Equals** Triggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error. - Trigger **New Agent** Triggered when a new Cursor cloud agent is created. - Action **Add Followup Instruction to Agent** Sends a follow-up instruction to an existing Cursor cloud agent, either starting a new run or steering the run in progress. Returns the new run or how the steer was delivered. - Action **Cancel run** Cancels the active run of a Cursor cloud agent. The run ends in the Cancelled state; start a new run to continue the conversation. - Action **Delete Agent** Permanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent. - Action **Find Agent Status** Looks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link. - Action **Get run** Returns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent. - Action **Launch Agent** Creates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run. - Action **List agents** Returns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL. - Action **List artifacts** Returns the files a Cursor cloud agent has produced, with each file's path, size and last modified time. Returns at most 100 artifacts. - Action **List models** Returns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants. - Action **List repositories** Returns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation. - Action **List runs** Returns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply. ## Each app on its own - [ **Azure Service Bus** Managed message broker providing queues and pub/sub topics for reliable, asynchronous communication between...](https://apiant.ai/connections/azure-service-bus) - [ **Cursor** Cursor is an AI-powered code editor that understands your codebase, supports natural-language coding...](https://apiant.ai/connections/cursor) Reviews ## What our customers say ## More from Azure Service Bus - [ **Azure Service Bus to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/azure-service-bus-to-hubspot) - [ **Azure Service Bus to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/azure-service-bus-to-salesforce) - [ **Azure Service Bus to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/azure-service-bus-to-slack) - [ **Azure Service Bus to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/azure-service-bus-to-google-sheets) - [ **Azure Service Bus to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/azure-service-bus-to-gmail) - [ **Azure Service Bus to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/azure-service-bus-to-google-calendar) ## More into Cursor - [ **ActiveCampaign to Cursor** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-cursor) - [ **Airtable to Cursor** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-cursor) - [ **Asana to Cursor** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-cursor) - [ **ClickUp to Cursor** ClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.](https://apiant.ai/connect/clickup-to-cursor) - [ **Brevo to Cursor** Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...](https://apiant.ai/connect/brevo-to-cursor) - [ **Calendly to Cursor** Calendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...](https://apiant.ai/connect/calendly-to-cursor) Questions ## Azure Service Bus and Cursor, answered ### ### What can start an automation from Azure Service Bus? Any of Azure Service Bus's 1 trigger in the catalog, including New Message in Queue. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Cursor when something happens in Azure Service Bus? Any of Cursor's 11 actions, including Add Followup Instruction to Agent, Find Agent Status, Get run and Launch Agent. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Cursor to Azure Service Bus? Yes. When something happens in Cursor, your agent can act in Azure Service Bus too. This page covers both directions: Cursor's triggers and Azure Service Bus's actions are listed here as well. ### ### Do I have to build a connector for Azure Service Bus or Cursor? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use Azure Service Bus and Cursor without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.