ilert

by iLert

180 downloads

Not rated

GitHub

About

Interact with [ilert](https://ilert.com) through natural language.

Details

Author: iLert
Downloads: 180
Categories: Developer Tools, Other

- Retrieve current authenticated user profile (ID, name, email, role, timezone, language)
- Search users by name/email with role filtering and pagination
- List alerts filtered by status (PENDING, ACCEPTED, RESOLVED), assignee, and date ranges
- Accept, resolve, escalate, reroute, and collaborate on alerts
- Create alerts and incidents with custom details and assignments
- Discover services, escalation policies, and on-call schedules
- List and execute automated actions and webhooks on alerts

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name ilert

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

From the repository

The server exposes multiple tools that can be invoked through an MCP client. Each tool has a specific purpose and accepts parameters as described in the tool list. No configuration or installation instructions are provided in this README.

`get-my-profile`

Get the current authenticated user's profile information. This tool provides current user context that is useful for other tools. This tool should be called for user context before working with alerts of the current user. Returns user ID, name, email, role, timezone, language, and other profile details needed for subsequent alert operations. Use this to determine user permissions, timezone for date filtering, and to establish the user's alert ownership context. The returned user ID can be used with list-alerts (assignedTo parameter) to get 'my alerts'.

`find-users`

Search and retrieve users with optional filtering. This tool provides user IDs that are required by other tools. Use this to find users by name or email, check user roles and permissions, and get user IDs for adding responders or assigning alerts. The returned user IDs can be used with: add-responder-to-alert (userId parameter), create-alert (responders array), and list-alerts (assignedTo parameter).

`list-alerts`

Retrieve alerts with flexible filtering options. This tool provides alert IDs that are required by other alert management tools. Key usage patterns: (1) Personal alerts - include the user's ID in 'assignedTo' parameter (2) All/team alerts - leave 'assignedTo' empty or specify multiple user IDs. The 'states' parameter filters by status - only use when specifically requested, otherwise defaults to active alerts (PENDING + ACCEPTED). Supports pagination and can include escalation details. The returned alert IDs can be used with: show-alert-details, accept-alert, resolve-alert, comment-alert, escalate-alert, reroute-alert, add-responder-to-alert, list-alert-action, and invoke-alert-action tools.

`show-alert-details`

Retrieve comprehensive details about a specific alert including all metadata, status information, and context needed for incident response. This tool requires an alert ID from list-alerts tool. Returns: alert summary and description, current status (PENDING/ACCEPTED/RESOLVED), all current responders and their status, escalation policy and rules, alert source and integration details, priority level, creation and update timestamps, next escalation information, assigned user details, and any custom fields. Use this tool before taking any actions on an alert to understand the full context, current ownership, and available escalation paths.

`accept-alert`

Accept responsibility for an open alert and begin working on it. This tool requires an alert ID from list-alerts tool. This action changes the alert status from PENDING to ACCEPTED, marking you as the active responder. Prerequisites: (1) Alert must be in PENDING status, (2) Alert must be assigned to the current user through escalation policy or manual assignment. Once accepted, you can add investigation comments, escalate to higher levels if needed, add additional responders for collaboration, or resolve the alert when the incident is fixed. This creates an audit trail showing when responsibility was taken.

`resolve-alert`

Mark an alert as resolved. This tool requires an alert ID from list-alerts tool. This action changes the alert status to RESOLVED and closes the incident. Only works on ACCEPTED or PENDING alerts that are assigned to the current user. Use this when the incident has been fully addressed and resolved. Ask the user to add a comment before resolving to document the resolution details.

`comment-alert`

Add a comment to an alert. This tool requires an alert ID from list-alerts tool, and content (the comment text). Comments are visible to all users assigned to the alert and help track progress or provide updates on the incident. Use this to document investigation steps, status updates, resolution details, or any relevant information about the alert. Comments are timestamped and help maintain a complete audit trail of the incident.

`escalate-alert`

Escalate an alert to the next level or specified escalation policy. This tool requires an alert ID from list-alerts tool. Use this when the current responder cannot handle the alert and it needs to be escalated to another person or team.

`reroute-alert`

Reroute an alert to a different escalation policy or team. This tool requires an alert ID from list-alerts tool and an escalation policy ID from find-escalation-policies tool. Use this to redirect an alert to the appropriate team when it was initially assigned incorrectly or needs different expertise.

`add-responder-to-alert`

Add additional team members as responders to an existing alert for collaboration and expertise. This tool requires an alert ID from list-alerts tool and optionally a user ID from find-users tool or schedule ID from find-schedules tool. Use this when: (1) The current responder needs specialized knowledge from another team member, (2) The incident requires multiple people working together, (3) You want to involve subject matter experts, (4) The alert needs escalation to a specific person without changing the escalation policy. The added responder will receive notifications, can accept the alert, add comments, and help resolve the incident. Multiple responders can work on the same alert simultaneously, creating a collaborative incident response.

`create-alert`

Create a new alert manually. This tool can use various IDs from other tools: alert source IDs from find-alert-sources, escalation policy IDs from find-escalation-policies, and user IDs from find-users. Use this to create alerts for incidents that need immediate attention but weren't automatically detected by monitoring systems.

`list-alert-action`

List available actions for a specific alert. This tool requires an alert ID from list-alerts tool. Use this to see what actions can be performed on an alert before executing them. The returned webhook IDs can be used with invoke-alert-action tool.

`list-alert-actions`

List all available alert actions across the system. This tool provides webhook IDs that are required by other tools. Use this to discover what automated actions, integrations, and workflows are available that can be triggered on alerts. This shows global alert actions that can be invoked, along with their webhook IDs needed for the invoke-alert-action tool. Use this before invoking alert actions to find the correct webhook ID. The returned webhook IDs can be used with: invoke-alert-action (webhookId parameter).

`invoke-alert-action`

Invoke a specific action on an alert. This tool requires an alert ID from list-alerts tool and a webhook ID from list-alert-action or list-alert-actions tools. Use this to perform automated remediation steps, trigger integrations, or invoke custom workflows associated with an alert. Workflow: 1) Use list-alert-action to find available actions for a specific alert, 2) Use the webhookId from that response in this tool. Example: { alertId: 123, webhookId: 456 }

`find-alert-sources`

Search and retrieve alert sources with optional filtering. This tool provides alert source IDs that are required by other tools. Use this to find available alert sources by name, view their IDs and integration details, and understand what sources can be used when creating alerts. Alert sources represent integrations like monitoring tools, applications, or manual sources that can generate alerts. The returned data includes source IDs needed for alert creation. The returned alert source IDs can be used with: create-alert (alertSource.id field).

`find-escalation-policies`

Search and retrieve escalation policies with optional filtering. This tool provides escalation policy IDs that are required by other tools. Use this to find escalation policies by name, view policy details, get policy IDs for creating alerts or rerouting, and understand escalation routing rules with level information. The returned escalation policy IDs can be used with: reroute-alert (escalationPolicyId parameter) and create-alert (escalationPolicy.id field).

`find-services`

Search and retrieve services with optional filtering. This tool provides service IDs that are required by other tools. Use this to find services by name, check service status, view service details, and get service IDs for creating incidents or alerts. The returned data prominently shows service IDs needed for other operations. The returned service IDs can be used with: create-incident (affectedServices.service.id field) and create-alert (optional alertSource.id field).

`create-incident`

Create a new incident to track major service disruptions or issues. This tool requires service IDs from find-services tool. Use this for coordinating incident response, communication, and resolution tracking for significant problems affecting multiple services or users.

`update-incident`

Update an existing incident. This tool requires incident ID from list-incidents tool. Use this to update the incident summary, status, message, and affected services.

`list-incidents`

Retrieve incidents with flexible filtering options. This tool provides incident IDs that are required by other incident management tools. The 'states' parameter filters by status - only use when specifically requested, otherwise defaults to all states (INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED). Supports pagination and filtering by service IDs and date ranges. The returned incident IDs can be used with: update-incident tool.

`find-schedules`

Find on-call schedules to see who is currently on duty. This tool provides schedule IDs that can be used by other tools. Returns schedule details including current and upcoming on-call rotations. The returned schedule IDs can be used with: add-responder-to-alert (scheduleId parameter) to add schedules as responders to alerts.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "ilert": {
            "ilert": {
                "type": "streamableHttp",
                "url": "https://mcp.ilert.com/mcp",
                "headers": {
                    "Authorization": "Bearer {{YOUR-API-KEY}}"
                }
            }
        }
    }
}

McpServers

{
    "ilert": {
        "type": "streamableHttp",
        "url": "https://mcp.ilert.com/mcp",
        "headers": {
            "Authorization": "Bearer {{YOUR-API-KEY}}"
        }
    }
}

Available Tools:

- User Profile - Get current authenticated user's profile information including ID, name, email, role, timezone, and language settings
- User Search - Find users by name or email with role filtering (USER, ADMIN, STAKEHOLDER, GUEST, ACCOUNT_OWNER, RESPONDER) and pagination support
- Alert Listing - Retrieve alerts with filtering by status (PENDING, ACCEPTED, RESOLVED), assignee, date ranges, and pagination
- Alert Details - Get comprehensive alert information including status, ownership, escalation policy, source details, priority, and timestamps
- Alert Acceptance - Accept responsibility for PENDING alerts, changing status to ACCEPTED to begin incident response
- Alert Resolution - Mark ACCEPTED or PENDING alerts as RESOLVED when incidents are fully addressed
- Alert Comments - Add investigation notes, progress updates, and resolution details to maintain audit trails
- Alert Escalation - Escalate alerts to next level in escalation policy when current responder cannot handle
- Alert Rerouting - Redirect alerts to different escalation policies or teams when initial assignment is incorrect
- Alert Collaboration - Add additional users or on-call schedules as responders for team collaboration
- Alert Creation - Manually create alerts with custom summaries, details, priority levels, and responder assignments
- Incident Creation - Create service incidents with status tracking, impact levels, and affected service associations
- Service Discovery - Find and list available services with search capabilities and pagination
- Escalation Policies - Search escalation policies by name to understand routing rules and get policy IDs
- On-Call Schedules - Find on-call schedules to see current rotations and add schedules as alert responders
- Alert Actions - List available automated actions and webhooks that can be triggered on alerts
- Action Execution - Invoke specific alert actions via webhooks to trigger automated workflows and integrations
- Alert Sources - Find available alert sources and integrations for alert creation and management

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

get-my-profile

find-users

list-alerts

show-alert-details

accept-alert

resolve-alert

comment-alert

escalate-alert

reroute-alert

add-responder-to-alert

create-alert

list-alert-action

list-alert-actions

invoke-alert-action

find-alert-sources

find-escalation-policies

find-services

create-incident

update-incident

list-incidents

find-schedules

Claude Desktop / Cursor

McpServers

Available Tools:

Install

More like this

Sequential Thinking

Sentry

Github

Filesystem

EverArt

Google Drive

`get-my-profile`

`find-users`

`list-alerts`

`show-alert-details`

`accept-alert`

`resolve-alert`

`comment-alert`

`escalate-alert`

`reroute-alert`

`add-responder-to-alert`

`create-alert`

`list-alert-action`

`list-alert-actions`

`invoke-alert-action`

`find-alert-sources`

`find-escalation-policies`

`find-services`

`create-incident`

`update-incident`

`list-incidents`

`find-schedules`