---
title: "Connect Cursor and ilert - APIANT.ai"
description: "When \"Agent Pull Request Created\" fires in Cursor, your agent runs \"Find User on Call\" in ilert."
canonical: "https://apiant.ai/connect/cursor-to-ilert"
---

# Connect Cursor and ilert

When **Agent Pull Request Created** fires in [Cursor](https://apiant.ai/connections/cursor), your agent runs **Find User on Call** in [ilert](https://apiant.ai/connections/ilert), or **New or Updated Incident** in ilert to **Add Followup Instruction to Agent** in Cursor. Describe the whole flow and it is built, tested on every scenario and kept running.

Cursor **3** triggers Cursor **11** actions ilert **1** trigger ilert **12** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Cursor and ilert 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 Cursor and ilert can do together

### From Cursor to ilert

- When **Agent Pull Request Created** in Cursor then **Find User on Call** in ilert
- When **New Agent** in Cursor then **Add Alert** in ilert

### From ilert to Cursor

- When **New or Updated Incident** in ilert then **Add Followup Instruction to Agent** in Cursor
- When **New or Updated Incident** in ilert then **Launch Agent** in Cursor

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 Cursor and ilert

## Triggers and actions 4 triggers · 23 actions

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

- Trigger

**New or Updated Incident**

Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.

- Action

**Accept Incident**

Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.

- Action

**Add Alert**

Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).

- Action

**Add maintenance window**

Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.

- Action

**Create Incident**

Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.

- Action

**Find User on Call**

Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.

- Action

**Get alert**

Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.

- Action

**Get incident**

Returns a single ilert incident by its id, including its status, severity, affected services and responders.

- Action

**Get maintenance window**

Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.

- Action

**List Alert Sources**

Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.

- Action

**List incidents**

Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.

- Action

**List users**

Returns the users in your ilert account, with their name, email, role and contact settings.

- Action

**Resolve Incident**

Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.

## Each app on its own

- [ **Cursor** Cursor is an AI-powered code editor that understands your codebase, supports natural-language coding...](https://apiant.ai/connections/cursor)
- [ **ilert** ilert is a platform for alerting, on-call management, and status pages.](https://apiant.ai/connections/ilert)

Reviews

## What our customers say

## More from Cursor

- [ **Cursor to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/cursor-to-hubspot)
- [ **Cursor to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/cursor-to-salesforce)
- [ **Cursor to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/cursor-to-slack)
- [ **Cursor to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/cursor-to-google-sheets)
- [ **Cursor to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/cursor-to-gmail)
- [ **Cursor to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/cursor-to-google-calendar)

## More into ilert

- [ **HubSpot to ilert** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-ilert)
- [ **Google Sheets to ilert** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-ilert)
- [ **Gmail to ilert** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-ilert)
- [ **Google Calendar to ilert** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-ilert)
- [ **Google Drive to ilert** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-ilert)
- [ **ActiveCampaign to ilert** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-ilert)

Questions

## Cursor and ilert, answered

###

### What can start an automation from Cursor?

Any of Cursor's 3 triggers in the catalog, including Agent Pull Request Created, New Agent and Agent Status Equals. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in ilert when something happens in Cursor?

Any of ilert's 12 actions, including Create Incident, Accept Incident, Add Alert and Add maintenance window. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from ilert to Cursor?

Yes. When something happens in ilert, your agent can act in Cursor too. This page covers both directions: ilert's triggers and Cursor's actions are listed here as well.

###

### Do I have to build a connector for Cursor or ilert?

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 Cursor and ilert 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.
