ilert MCP server

What the model can do

ilert alerting and on-call: alerts and incidents with their status and services, on-call schedules and who is on call, services with their status, and the alert sources, escalation policies and users behind them. Can raise, accept, assign, escalate, rename and resolve alerts, declare and update incidents, post incident status updates, schedule maintenance windows and add on-call overrides.

Reads

• ilert_alertsAlerts in ilert reported in a window (default the last 7 days): summary, status (PENDING, ACCEPTED, RESOLVED), priority, severity, source…
• ilert_incidentsIncidents in ilert declared in a window (default the last 30 days): title, status (DECLARED, INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED)…
• ilert_schedulesOn-call schedules in ilert with who is on the current shift and the next, the timezone and type.
• ilert_on_callsWho is on call in ilert, per escalation policy, level and schedule: now by default, or across a window of at most three months.
• ilert_servicesServices tracked in ilert with their current status (OPERATIONAL, UNDER_MAINTENANCE, DEGRADED, PARTIAL_OUTAGE, MAJOR_OUTAGE) and description.
• ilert_lookupsThe ids ilert's actions take: alert sources (name, status, escalation policy), escalation policies, or users (id and name only).

Acts, when you ask

These change something in ilert. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• ilert_create_alertRaise an alert in ilert on an alert source (ilert_lookups alert_sources).
• ilert_accept_alertAccept an ilert alert as the key's user, which stops it escalating further; everyone on the alert sees who accepted it.
• ilert_resolve_alertResolve an ilert alert, ending its escalation; the alert source and anyone following it see it resolved.
• ilert_assign_alertAssign an ilert alert to exactly one of a user, an escalation policy or an on-call schedule (ids from ilert_lookups and ilert_schedules).
• ilert_escalate_alertEscalate an ilert alert to a level of its escalation policy (0 is the first level), paging the people at that level.
• ilert_change_alert_summaryRename an ilert alert (change its summary).
• ilert_create_incidentDeclare an incident in ilert with a title and optionally a summary, status, severity (1 to 5) and the affected services with their impact…
• ilert_update_incidentChange an ilert incident's title, summary, status, severity or affected services; everything else on it is kept…
• ilert_post_incident_updatePost a status update (status and message) on an ilert incident.
• ilert_add_maintenance_windowSchedule a maintenance window in ilert, during which alerts from the given alert sources and services are suppressed: nobody is paged for them until…
• ilert_add_schedule_overridePut a user (ilert_lookups users) on call in an ilert schedule (ilert_schedules) for a period…

Connect it

First connect ilert on Dashboard → Connections, then add Memtro to your client once. The ilert tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared ilert connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Who is on call for web tonight?
• › What alerts fired overnight?
• › Are there any open alerts on checkout?
• › Which services are degraded right now?
• › Put Priya Sharma on call for web from 6pm to midnight tonight.

Questions

Is this an official ilert MCP server?

No. It is Memtro's MCP server with Memtro's ilert connector behind it: the connector reads ilert through its API with the credentials you connect on Dashboard → Connections, and ilert publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in ilert?

Only when you ask, and only what it has been granted: raise an ilert alert on an alert source (pages on-call); accept an ilert alert; resolve an ilert alert; assign an ilert alert to a user, escalation policy or schedule; escalate an ilert alert to a level of its policy; change an ilert alert's summary; declare an ilert incident (may notify subscribers); update an ilert incident's title, summary, status, severity or affected services; post a status update on an ilert incident; schedule an ilert maintenance window; put a user on call in an ilert schedule as an override. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server