# iLert — how to use (mcp.ai)

Connect your iLert account and use 8 tools for IT operations straight from your AI agent. Connect with your own API key. iLert is an incident response platform for managing alerts, on-call schedules, escalations, incidents, and status pages.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_ilert?ms=1787291520000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `ilert_get_alert`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/ilert`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/ilert/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/ilert/get/alert` — Get one iLert alert by its numeric ID, optionally expanding escalation rules, the next escalation user, or custom details.
  - body: { include?: string[], alert_id: integer }
- `POST https://api.mcp.ai/api/ilert/get/current/user` — Return the authenticated iLert user, including identity, role, timezone, and active team context. Use this to verify who the API key represents before incident-response work.
- `POST https://api.mcp.ai/api/ilert/get/incident` — Get one iLert status incident by numeric ID, optionally including subscription state, affected teams, or history.
  - body: { include?: string[], incident_id: integer }
- `POST https://api.mcp.ai/api/ilert/list/alerts` — List iLert alerts with optional state, source, escalation-policy, responder, and report-time filters. Returns one page and a continuation cursor.
  - body: { states?: string[], from_time?: string, policy_ids?: integer[], source_ids?: integer[], until_time?: string, max_results?: integer, next_cursor?: string, responder_ids?: string[], include_next_escalation_user?: boolean }
- `POST https://api.mcp.ai/api/ilert/list/incidents` — List iLert status incidents with optional lifecycle-state, affected-service, and report-time filters. Returns one page and a continuation cursor.
  - body: { states?: string[], from_time?: string, until_time?: string, max_results?: integer, next_cursor?: string, service_ids?: integer[], include_subscribed?: boolean }
- `POST https://api.mcp.ai/api/ilert/list/on/calls` — Find who is on call for selected escalation policies, schedules, users, and a time window of at most three months. Returns one page and a continuation cursor.
  - body: { expand?: string, user_id?: integer, timezone?: string, from_time?: string, policy_id?: integer, until_time?: string, max_results?: integer, next_cursor?: string, schedule_id?: integer, policy_level?: object }
- `POST https://api.mcp.ai/api/ilert/list/resources` — List one incident-response resource catalog: services, teams, escalation policies, or maintenance windows. Use returned IDs as filters or references in alert, incident, and on-call tools.
  - body: { include?: string[], from_time?: string, member_id?: integer, source_ids?: integer[], until_time?: string, max_results?: integer, next_cursor?: string, service_ids?: integer[], resource_type: string, maintenance_state?: string }
- `POST https://api.mcp.ai/api/ilert/list/schedules` — List iLert on-call schedules, optionally expanding current or next shifts and schedule definitions. Returns one page and a continuation cursor.
  - body: { include?: string[], max_results?: integer, next_cursor?: string }

## Example prompts
- "What can I do in iLert?"
- "Show me a summary of my iLert account"

## More
- Page: https://mcp.ai/ilert
- Agent spec (llms.txt): https://mcp.ai/ilert/llms.txt
- Postman collection: https://mcp.ai/ilert/postman.json