mcp-ilert

Ilert MCP Server

ilert alert and incident workflows are available through mcp-ilert for on-call responders and incident teams. Its tools cover alert triage, ownership, escalation, collaboration, service incidents, and webhook-based actions.

Server facts

mcp-ilert

Project

Author
iLert
License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
17
Last commit
Data as of

Overview

On-call work in ilert connects user identity, alert ownership, and response routing. mcp-ilert exposes profile lookup and user search alongside alert discovery filtered by assignee, status, or dates. Responders can inspect an alert’s priority, source, escalation rules, timestamps, and assigned people before acting. Pending alerts assigned to the current user can be accepted, while pending or accepted alerts assigned to that user can be resolved. Comments record investigation progress and resolution context. When another responder or team is needed, tools support escalation, rerouting through a different policy, and adding people or on-call schedules.

Service disruption tracking extends beyond individual alerts. Teams can find services, create incidents associated with affected services, list incidents using service and date filters, and update their summaries, statuses, messages, or service associations. Manual alert creation draws on searchable alert sources, escalation policies, and users. For automation, separate discovery tools expose actions available globally or for a particular alert; their webhook identifiers are then used to invoke an action against that alert. Schedule lookup also exposes current and upcoming rotations to inform responder selection.

mcp-ilert setup notes

  • mcp-ilert records stdio only; confirm a network transport upstream before planning remote access.
  • mcp-ilert has no recorded license; confirm reuse terms in its repository.

Related MCP servers