AlertOps MCP Server
MCP server for AlertOps's incident alerting/on-call API - alerts, message topics, users and their contact methods, groups, configured inbound integrations, and on-call schedules, for AI assistants and the WYRE Conduit gateway.
Authentication
AlertOps' REST API (, per its published OpenAPI spec at ) authenticates with a static account-level , generated under . Unlike most WYRE Conduit sidecars, the key is not sent as a bearer token or custom auth header - AlertOps requires it as an , GET and POST alike (live-verified 2026-09-20: an invalid key returns a clean HTTP 401 on every endpoint this connector calls). This connector receives the key per-request via a custom header (never OAuth, same shape as every other static-key WYRE Conduit sidecar) and itself appends when calling AlertOps' API. In gateway mode the key arrives per-request via the header; in local/stdio mode it's read once from . HTTP also requires an signature (see HTTP authentication below). The HTTP server refuses to start without a real .