DevHelm MCP Server

Acquire a deploy lock to prevent concurrent deployments. Required: lockedBy (identity of requester, e.g. hostname or CI job ID). Optional: ttlMinutes (default 30, max 60).

Add a monitor to a resource group. Required fields: monitorId.

Add a custom domain to a status page. Required fields: hostname (e.g. "status.example.com"). Returns verification records (CNAME target and TXT token) that must be configured in your DNS before calling verify.

Add a subscriber to a status page (admin). Required fields: email.

Cancel a maintenance window — alerts resume immediately. Call this AFTER a deploy or maintenance operation completes successfully so any new monitor failures surface as real incidents instead of being silently absorbed. If the window was scheduled but not yet started, this prevents it from ever opening. The window record is removed; the audit log preserves the historical fact that the window existed. There is no "uncancel" — schedule a new window if you need to restore suppression.

Create a new alert channel. Required: name, type, config (type-specific). Types: SLACK, EMAIL, WEBHOOK, PAGERDUTY, OPSGENIE, TELEGRAM, DISCORD, MSTEAMS.

Create a new API key. The key value is returned only once. Required fields: name. Optional: expiresAt.

Create an environment. Required fields: name, slug, color.

Create a manual incident. Required fields: title, severity (DOWN/DEGRADED/MAINTENANCE). Optional: monitorId (UUID), body (detailed description).

Schedule a maintenance window to suppress alerts during planned work. Call this BEFORE running an operation that may legitimately cause monitors to fail — a deploy, a database migration, a third-party service's announced downtime — so the on-call rotation isn't paged for known-expected failures. Always pair every successful create with a follow-up ``cancel_maintenance_window`` once the operation finishes; if the operation runs long, call ``update_maintenance_window`` to push the end time back rather than letting the window lapse early. Time fields use ISO 8601 / RFC 3339 timestamps with explicit timezone — UTC strongly preferred. Example: ``"2026-05-15T14:00:00Z"``. Naive timestamps (no timezone) are rejected by the API. Body fields: - ``startsAt`` (required): when the window opens. - ``endsAt`` (required): when the window closes; must be strictly after ``startsAt``. - ``monitorId`` (optional): UUID of a single monitor to scope the window to. Omit (or set null) to make this an **org-wide window** that suppresses alerts on every monitor in the workspace — the right choice for a deploy or migration that touches the whole platform. - ``reason`` (optional): human-readable explanation ("v0.7.3 deploy", "Postgres major upgrade"). Surfaces in the dashboard and on-call channel; keep it specific. - ``repeatRule`` (optional): iCal RRULE string for recurring windows (max 100 chars), e.g. ``FREQ=WEEKLY;BYDAY=SU`` for weekly Sunday maintenance. Omit for one-time windows. - ``suppressAlerts`` (optional): whether the window actually silences alerts. Default ``true``; set ``false`` to record a maintenance window for audit without changing alerting behavior.

Create a new uptime monitor. Required fields: name, type (HTTP/DNS/TCP/ICMP/MCP/HEARTBEAT), config (type-specific), frequencySeconds (30-86400). ``managedBy`` is set automatically to ``MCP`` server-side; callers cannot override it. Use the SDK or CLI directly if you need a different attribution.

Create a notification policy. Required: name, matchRules (list of {type, value?, monitorIds?, regions?}), escalation ({steps: [{delayMinutes, channelIds}], onResolve?, onReopen?}), enabled (bool), priority (int, higher = evaluated first).

Create a resource group. Required fields: name. Optional: description.

Create an encrypted secret. Required fields: key, value. The value is encrypted at rest and can be referenced in monitor auth configs as {{secrets.KEY}}.

Create a new status page. Required fields: name, slug. Optional: description, branding (brandColor, theme, headerStyle, etc.), visibility (PUBLIC/PASSWORD), enabled, incidentMode (MANUAL/REVIEW/AUTOMATIC).

Add a component to a status page. Required fields: name, type (STATIC or MONITOR). Optional: groupId (nest under a group), monitorId (for MONITOR type).

Create a component group on a status page. Required fields: name.

Create an incident on a status page. Required fields: title, impact (NONE/MINOR/MAJOR/CRITICAL). Optional: body, status (INVESTIGATING/IDENTIFIED/MONITORING/RESOLVED), affectedComponents (list of {componentId, status}).

Create a tag. Required fields: name. Optional: color.

Create a webhook endpoint. Required fields: url, events (list of event types to subscribe to).

Delete an alert channel.

Delete an API key permanently.

Stop tracking a service dependency.

Delete an environment by slug.

Delete a monitor permanently.

Delete a notification policy.

Delete a resource group.

Delete a secret by key.

Delete a status page permanently.

Remove a component from a status page.

Delete a component group from a status page.

Delete a status page incident permanently.

Delete a tag.

Delete a webhook endpoint.

Dismiss a draft incident (deletes it without publishing).

Force-release any active deploy lock (admin action).

Get an alert channel by ID.

Everything the detection engine recorded for a single check. Includes the rule evaluations produced for this check_id, the state transitions that fired (if any), and the policy snapshot active at evaluation time. Use when a user references a specific check execution ID (e.g. from a support ticket or webhook).

Get the currently active deploy lock, or null if unlocked.

Get a tracked dependency by ID.

Get an environment by slug (e.g. 'production', 'staging').

Get a single incident by ID with full details.

Full forensic timeline for an incident. Returns every recorded state transition for the incident, the rule evaluations that caused each triggering transition, and the policy snapshot in effect at the time. Use this to explain why an incident was declared/confirmed/resolved, or to audit a past detection decision.

Get a single maintenance window by ID with full details.

Get a single monitor by ID, including its full configuration.

Get a notification policy by ID.

Fetch a policy snapshot by its content-addressed SHA-256 hash. Useful for inspecting the exact detection policy that was active when a specific evaluation or transition happened — the hash is stable, so historical data keeps pointing at the right policy even if the monitor has been edited since.

Get a resource group by ID.

Get the dashboard overview with monitor counts, incident summary, and uptime stats.

Get a status page by ID, including branding and overall status.