Get started

iLert for AI agents

iLert is an incident response platform for managing alerts, on-call schedules, escalations, and status pages. Engineering teams rely on it to keep this visible during day-to-day operations. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect iLertSee the 8 actions ↓
DevOps and monitoringAPI keyMCP + RESTilert.com
AUDIT LOG · ILERTPOLICY: acme-support
09:41:07 · claude · u_8f2read
ilert.list_alerts
List Alerts✓ allowed · 212ms
09:41:08 · claude · u_8f2read
ilert.get_alert
Get Alert✓ allowed · 164ms
EVERY ILERT CALL, ON THE RECORD
01 · USE CASES

What agents do in iLert.

01

Check who is on call

List current on-call schedules to know who to page for an active incident.

02

Pull an incident's details

Fetch a specific incident's timeline and status to update a stakeholder.

03

List open alerts

List currently open alerts across services, read-only, to triage what needs attention.

02 · ACTIONS

8 iLert actions, graded by risk.

Every iLert action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

8

Look things up. Allowed by default.

  • ilert.get_alert
    Get Alert
  • ilert.list_alerts
    List Alerts
  • ilert.get_incident
    Get Incident
  • ilert.list_on_calls
    List On Calls
  • ilert.list_incidents
    List Incidents
  • ilert.list_resources
    List Resources
  • ilert.list_schedules
    List Schedules
  • ilert.get_current_user
    Get Current User

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

iLert in three steps.

  1. 01Your users connect iLertThey add their iLert api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 03Any agent can actYour agent calls iLert through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('ilert', {
  read: 'allow',
  write: 'ask',        
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How iLert connects.

Users add their iLert api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same iLert connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use iLert from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More devops and monitoring apps.

PagerDuty368 actionsServiceNow171 actionsNew Relic159 actionsGrafana Cloud118 actionsBetter Stack117 actionsDatadog65 actionsMezmo36 actionsStatuscake30 actions
ALL DEVOPS AND MONITORING APPS →
07 · FAQ

iLert and Arc0, answered.

Q01

Can I use iLert with Claude, ChatGPT or Cursor?

Yes. Connect iLert to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the iLert actions you allow.

Q02

How do users connect iLert?

Users add their iLert api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which iLert actions can my agent take?

8 in total: 8 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in iLert?

Yes. Allow read actions and deny writes in the iLert policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call iLert too?

Yes. The same iLert connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug iLert into your agent.

Your users connect iLert once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.

Connect iLertBrowse all apps →

Free to build · MCP + REST · Audit log on every plan