Overview
MonoDuty connects your assistant to your monitoring and on-call workspace. Inspect active alerts, review monitoring coverage and alerting readiness, and prepare instrumentation proposals for administrator review. With separate creation permission, create services, public HTTP(S) Monitors, Heartbeats and incoming Webhook sources. With management permission, inspect resources and perform supported updates, pauses, resumes, deletion or incident resolution. Each action remains subject to workspace ownership, plan limits and the permissions you grant. Sign in with an active, verified MonoDuty account, choose a workspace where you have administrator access, and connect with an API-eligible plan. A connection stays bound to the selected workspace. Proposal-only access does not activate monitoring. Provide application context through your assistant; the remote server does not independently inspect local code. MCP tools do not send test alerts, and a configured resource does not prove notification delivery. Verify delivery separately with a controlled test.
