# iLert — MCP server on 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.

By: mcp.ai · official
Page: https://mcp.ai/ilert

## Connect (MCP protocol)
Remote MCP endpoint (HTTP, streamable): https://api.mcp.ai/p_ilert?ms=1787291520000
Add it as a custom/remote MCP connector, then authenticate when prompted.

## REST API (no MCP client required)
Every tool is also a REST endpoint, authed with a workspace API key.
Discover: GET https://api.mcp.ai/api/ilert/_endpoints   # public; lists every endpoint
Call:     POST https://api.mcp.ai/api/ilert/<endpoint>
  Authorization: Bearer sk_live_…   # create one at https://mcp.ai/settings/api-keys
  Content-Type: application/json
  Body: { …args }   →   { "ok": true, "tool": "<id>", "result": { … } }

## Developer docs
How to use (MCP or REST), markdown: https://mcp.ai/ilert/skill.md
Postman collection (v2.1): https://mcp.ai/ilert/postman.json

## Tools
- ilert_get_alert(include?: string[], alert_id: integer) — Get one iLert alert by its numeric ID, optionally expanding escalation rules, the next escalation user, or custom details.
- 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.
- ilert_get_incident(include?: string[], incident_id: integer) — Get one iLert status incident by numeric ID, optionally including subscription state, affected teams, or history.
- ilert_list_alerts(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) — List iLert alerts with optional state, source, escalation-policy, responder, and report-time filters. Returns one page and a continuation cursor.
- ilert_list_incidents(states?: string[], from_time?: string, until_time?: string, max_results?: integer, next_cursor?: string, service_ids?: integer[], include_subscribed?: boolean) — List iLert status incidents with optional lifecycle-state, affected-service, and report-time filters. Returns one page and a continuation cursor.
- ilert_list_on_calls(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) — 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.
- ilert_list_resources(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) — 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.
- ilert_list_schedules(include?: string[], max_results?: integer, next_cursor?: string) — List iLert on-call schedules, optionally expanding current or next shifts and schedule definitions. Returns one page and a continuation cursor.

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

## Links
Docs: https://mcp.ai/docs/mcps/ilert
Website: https://mcp.ai/mcps/ilert