ilert

You can integrate ilert as an MCP server to let AI assistants navigate your alerting and incident management resources. This server enables streamlined access to ilert data and actions through a remote MCP endpoint, reinforcing automation and assistant-driven workflows across your team.

How to use

You connect an MCP client to the ilert MCP server using either the remote HTTP endpoint or a local command-based runtime. The HTTP option provides a straightforward remote connection, while the local runtime lets your client run a small MCP bridge on your side. Once connected, you can query alerts, incidents, and other resources, issue actions, and have your assistant read statuses or trigger workflows within ilert.

How to install

Prerequisites: you need Node.js and npm installed on your machine. If you plan to run a local MCP bridge, you will also use npx or npm to execute the bridge command.

{
  "mcpServers": {
    "ilert_http": {
      "type": "http",
      "url": "https://mcp.ilert.com/mcp",
      "args": []
    },
    "ilert_stdio": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.ilert.com/mcp",
        "--header",
        "Authorization: Bearer ${ILERT_AUTH_TOKEN}"
      ],
      "env": {
        "ILERT_AUTH_TOKEN": "YOUR-API-KEY"
      }
    }
  }
}

# Install prerequisites (example for macOS/Linux)
# 1) Install Node.js and npm if you don't have them
# - On macOS with Homebrew: brew install node
# - On Debian/Ubuntu: sudo apt-get install nodejs npm

# 2) If you want to try the HTTP endpoint, you mainly need network access and an API key
# 3) If you want to run the local MCP bridge via npx, you must have npm available

# 4) Prepare your API key (see the ILERT workflow for generating API keys)

Additional sections

Configuration notes: you have two connection methods to choose from. Use the HTTP method for a remote, managed MCP connection to https://mcp.ilert.com/mcp. If your environment cannot reach remote MCP endpoints or you need to run a local bridge, use the stdio configuration to execute the MCP bridge via npx with the required header for authentication.

Security: protect your API key. Store the Bearer token securely and provide it to your MCP client through a safe mechanism, such as environment variables or a secrets manager. For the local bridge, keep the ILERT_AUTH_TOKEN value out of source control and only load it at runtime.

Troubleshooting tips: if you cannot connect to the HTTP endpoint, verify that your network allows outbound connections to mcp.ilert.com and that the API key is valid. If the local bridge fails to start, ensure that Node.js and npm are properly installed and that ILERT_AUTH_TOKEN is available in the environment when the bridge executes.