otherapi_key

iLert

iLert is an incident response platform for managing alerts, on-call schedules, escalations, incidents, and status pages.

Integration

Vendor
iLert
Category
other
Auth
API_KEY
Tools
8
Composio slug
ilert

Tools

  • Get Alert

    Get one iLert alert by its numeric ID, optionally expanding escalation rules, the next escalation user, or custom details.

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

  • Get Incident

    Get one iLert status incident by numeric ID, optionally including subscription state, affected teams, or history.

  • List Alerts

    List iLert alerts with optional state, source, escalation-policy, responder, and report-time filters. Returns one page and a continuation cursor.

  • List Incidents

    List iLert status incidents with optional lifecycle-state, affected-service, and report-time filters. Returns one page and a continuation cursor.

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

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

  • List Schedules

    List iLert on-call schedules, optionally expanding current or next shifts and schedule definitions. Returns one page and a continuation cursor.

Setup

  1. Create or open a Switchy Project.
  2. Open Integrations and connect iLert.
  3. Authorise through api_key. Switchy stores the connection against your org.
  4. Everyone in the Project can now @-mention the iLert tools in chat.

What teammates see: by default, memories from iLert are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Starter prompts for this model will land here soon.

More other MCPs

See all other MCPs

Data last verified 7 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.