ilert MCP server (hosted)

The ilert MCP Server is the official Model Context Protocol (MCP) endpoint for ilert. It enables AI agents, coding assistants, and autonomous systems to query, analyze, and act on your ilert resources — including alerts, incidents, services, on-call schedules, and more.

---

🔗 Overview

• Base URL: https://mcp.ilert.com/mcp

• Transport: Streamable HTTP

• Authentication: API key (Bearer token)

• Host: ilert (no local installation required)

This hosted MCP server provides a secure, out-of-the-box connection for your AI assistants such as Claude, Cursor, Cline, Windsurf, or any MCP-compliant client.

---

🚀 Quick Installation

You can install and connect the ilert MCP server directly to a compatible AI assistant using the button below:

---

🔑 Authentication

The ilert MCP Server uses API key authentication.

1. Log in to your ilert account.

2. Go to Profile → API Keys.

3. Create a new API key for your user.

4. Copy the key and use it in the configuration examples below.

---

⚙️ Configuration Examples

Option 1 — Streamable HTTP (Preferred)

Use this configuration for clients that support remote MCP servers and Streamable HTTP transport:

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

This configuration works with most modern AI assistants such as Cursor, Claude Desktop, Cline, and Windsurf.

---

Option 2 — Using mcp-remote (Fallback)

For clients that do not yet support Streamable HTTP, you can use the mcp-remote CLI bridge:

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

This configuration proxies the connection to the hosted ilert MCP endpoint via the local mcp-remote process.

---

🧠 What You Can Do with the ilert MCP Server

Once connected, your AI agent can:

• Retrieve and inspect alerts, incidents, and on-call schedules

• Analyze alert timelines, incident communications, and root cause data

• Correlate alerts with deployment events, status pages, or GitHub commits

• Automatically trigger AI investigation agents within ilert

---

📚 Additional Resources

• Model Context Protocol (MCP) Specification

• ilert Developer Documentation

• ilert AI & Automation Overview

---

🧩 Troubleshooting

Issue	Possible Cause	Solution
401 Unauthorized	Missing or invalid API key	Verify that your API key is active and copied correctly.
Connection refused	MCP client doesn’t support Streamable HTTP	Use the mcp-remote configuration instead.
Empty responses	API key with limited scope	Ensure your key has sufficient permissions for alert and incident access.

---

🛡️ Security Notes

• The MCP server never stores your API key — it’s passed directly in the request header.

• The connection uses HTTPS with Streamable HTTP transport for secure, bidirectional communication.

• You can revoke API keys anytime from your ilert user settings.