
The REST API can return each monitor’s assigned alert contacts, with their threshold and recurrence, when showMonitorAlertContacts=1 is passed. The MCP server doesn’t expose that option. list-monitors has no parameter for it, and get-monitor-details doesn’t return assignedAlertContacts.
As a result, alert contacts can be set through the MCP with create-monitor and update-monitor but can’t be read back. That makes it impossible to confirm a new monitor’s alert routing or to audit routing across an account without falling back to the REST API and a separate API key.
Request: add a showMonitorAlertContacts option to list-monitors, and return assignedAlertContacts (alertContactId, threshold, recurrence) in get-monitor-details.