DevHelm MCP Server

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), body. Optional: status (INVESTIGATING/IDENTIFIED/MONITORING/RESOLVED), affectedComponents (list of {componentId, status}), notifySubscribers. To schedule a maintenance window, use create_status_page_maintenance.

Create a maintenance window on a status page. Required fields: title, impact (NONE/MINOR/MAJOR/CRITICAL), body, scheduledFor (ISO 8601). Optional: scheduledUntil, autoResolve, status, affectedComponents, notifySubscribers.

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

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

Create a webhook testing inbox and return its capture ``httpUrl``. Required: name. Optional: status, httpResponse (mock reply), cors, retentionDays, maxEvents.

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 status page maintenance window permanently.

Delete a tag.

Delete a webhook endpoint.

Dismiss a draft incident (deletes it without publishing).

Dismiss a draft maintenance window (deletes it without publishing).

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

Get an alert channel by ID.

Get daily uptime history for every leaf component of a catalog service in one call, keyed by component ID, over a period ('7d', '30d', '90d', '1y'; default '30d'). Prefer this over repeated get_component_uptime calls when comparing components.

Get a single API key's metadata by id. The secret value is never returned.

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 daily uptime history for a single component of a catalog service (e.g. just the 'API' component of Stripe) over a period ('7d', '30d', '90d', '1y'; default '30d'). Get component IDs from list_service_components.

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

Get a tracked dependency by ID.

Get an email testing domain, including the DNS records to set.

Get one captured message (headers, text, html, otp, links).

Get the stored message source as text (capped at 64 KB).

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 the newest message at a full address without waiting. Returns ``{"message": null}`` when nothing has arrived yet.

Get the newest request captured by an inbox without waiting. Returns ``{"event": null}`` when nothing has arrived yet.

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 a catalog service's summary by slug (e.g. 'github'), including its current status, categories, and component overview.

Get a one-day rollup for a catalog service on a UTC calendar day (ISO YYYY-MM-DD): aggregated uptime, per-component impact windows, and the incidents that overlapped that day. Use this to answer 'what happened to Stripe on 2026-06-01?'.

Get one vendor incident in full detail, including the vendor's timeline of status updates (investigating → identified → resolved). Get incident IDs from list_service_incidents.

Get the live (real-time) operational status of a catalog service, fetched from its upstream status page. Use this when freshness matters more than latency — e.g. 'is Stripe down right now?'.

Get historical uptime stats for a catalog service over a period (e.g. '7d', '30d', '90d'; default '30d').

Get the global status summary across the entire service catalog — counts of operational / degraded / outage services. Use this for a quick 'is anything broken on the internet right now?' overview before drilling into a specific service.

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

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

Get a status page incident with its full timeline of updates.

Get a status page maintenance window with its full timeline of updates.

Get a tag by ID.

Get a webhook endpoint by ID.

Get one captured request with headers and body (capped at 64 KB).

Get a webhook testing inbox, including its capture ``httpUrl``.

Deliver a test message to an address without SMTP. Uses the same capture path as real mail, so waits and extraction behave the same. Returns ``eventId``, ``receivedAt`` and ``inbox``.

List all alert channels configured in the workspace.

List all API keys in the workspace.

List all tracked service dependencies.

Hourly received-message counts for the last 24 h, per domain ID.

List email testing domains (assigned and custom) in the workspace.

List links extracted from a message (verification, reset, ...).

List messages received at a full address, newest first. ``limit`` defaults to 20 (max 50); pass ``nextCursor`` back as ``cursor`` for the next page. ``q`` filters on subject and sender.

List one-time codes extracted from a message.

List all environments in the workspace.

List all incidents in the workspace.

List maintenance windows for the workspace. Use this BEFORE creating a new window to check whether someone else (or an earlier agent run) already scheduled overlap, or AFTER a deploy to confirm the window you opened is still active. Filters (all optional; combine freely): - ``monitor_id``: UUID of a monitor — only windows attached to that single monitor (org-wide windows are excluded). - ``status``: ``"active"`` for windows currently in progress, or ``"upcoming"`` for windows scheduled in the future. Past / cancelled windows are not returned by the API today; omit ``statu…

List recent check results for a monitor (cursor-paginated).

List rule evaluations produced for a monitor (paginated). Filters: - rule_type: e.g. "consecutive_failures", "latency_threshold" - region: probe region, e.g. "us-east" - only_matched: if True, return only evaluations that fired - from_/to: ISO-8601 datetime bounds Use to answer "which rules fired on monitor X in the last hour?".

List state transitions recorded for a monitor (paginated). A transition captures every WATCHING→TRIGGERED→CONFIRMED→RESOLVED edge the detection engine walked. Includes transitions that occurred before an incident was declared (incident_id = null). Use to reconstruct the full reliability history of a monitor.

List version history for a monitor.

List all uptime monitors in the workspace.

List all notification policies in the workspace.

List all resource groups in the workspace.

List all secrets (metadata only, values are never returned).

List all service catalog categories (e.g. cloud, payments, devtools) usable as the `category` filter in search_services.

List a catalog service's components (e.g. 'API', 'Dashboard', 'Webhooks') with their individual statuses. Component IDs can be used to track a single component via track_dependency.

List incidents for a catalog service, or across all services when `slug` is omitted. Filter by `status` (e.g. 'active', 'resolved') to answer questions like 'which of my dependencies have open incidents?'.

List scheduled and past maintenance windows announced by a catalog service (e.g. upcoming AWS maintenance that could affect you).

List all components on a status page.

List custom domains on a status page.

List component groups on a status page (with nested components).

List incidents on a status page (paginated).

List maintenance windows on a status page (paginated).

List confirmed subscribers on a status page (paginated).

List all status pages in the workspace.

List all tags in the workspace.

List requests captured by an inbox, newest first. ``limit`` defaults to 20 (max 50); pass ``nextCursor`` back as ``cursor`` for the next page. Rows carry a body preview only.

Hourly received-request counts for the last 24 h, per inbox ID.

List webhook testing inboxes in the workspace.

List all webhook endpoints in the workspace.

Pause a monitor (stops checking until resumed).

Post a timeline update on a status page incident. Required fields: body (message text), status. Optional: notifySubscribers (default true), affectedComponents (list of {componentId, status}).

Post a timeline update on a status page maintenance window. Required fields: body (message text), status. Optional: notifySubscribers (default true), affectedComponents (list of {componentId, status}).

Publish a draft incident (sets it live, notifies subscribers). Use update_status_page_incident first if you need to change the draft's title, impact, status, body, or affected components before publishing.

Publish a draft maintenance window (sets it live, notifies subscribers).

Release a deploy lock by ID.

Remove a monitor from a resource group.

Remove a custom domain from a status page.

Remove a subscriber from a status page.

Reorder components on a status page. Required: positions — list of {componentId, position} entries giving every component its new zero-based ordinal. The full set must be provided; partial reorders are rejected by the API.

Batch-reorder a status page's full layout. Required: sections — top-level layout in their new order, where each entry is either {kind:"component", componentId} or {kind:"group", groupId}. Use ``groupOrders`` (optional) to also reorder components within specific groups; only include groups whose internal order changed. The full top-level set must be provided — partial reorders are rejected by the API. Use this for "drag-and-drop" layout edits that touch both groups and ungrouped components. To reorder components within a single group only, prefer ``reorder_status_page_components``.

Resolve an active incident, optionally with a resolution message.

Resume a paused monitor.

Revoke an API key (disables it without deleting).

Search the catalog of third-party services (Stripe, GitHub, AWS, ...) that can be tracked as dependencies. Use `query` for free-text search by name (e.g. 'stripe', 'cloudflare') and `category` to filter by catalog category (see list_service_categories). Results are paginated; raise `limit` (default 20) for broader sweeps.

Send a test notification to an alert channel to verify it works.

Trigger an ad-hoc test run for a monitor and return the result.

Send a test dispatch to verify a notification policy's routing.

Send a test event to a webhook endpoint to verify it works.

Start tracking a service dependency by its slug (e.g. 'github', 'aws'). Optionally track a single component via `component_id` (see list_service_components) and set `alert_sensitivity`: AWARENESS (silent tracking, default), INCIDENTS_ONLY, MAJOR_ONLY, or ALL.

Update an existing alert channel. Updatable fields: name, type, config (type-specific). See create_alert_channel for supported types.

Change how loudly a tracked dependency alerts you. Levels: AWARENESS (silent tracking, default — status visible on the dashboard but no notifications), INCIDENTS_ONLY (notify on any incident), MAJOR_ONLY (notify only on major/critical incidents), and ALL (every status change, including maintenance).

Enable (``active``) or disable (``disabled``) mail capture on a domain.

Update an environment by slug.

Update an in-flight or scheduled maintenance window. The most common use is **extending** an active window when a deploy runs longer than expected — call this with the new ``endsAt`` to keep alerts suppressed past the original deadline. The endpoint is a full replacement (PUT, not PATCH): pass the complete intended state, not a delta. Any field omitted falls back to the underlying model's default rather than preserving the existing value. Time fields use ISO 8601 / RFC 3339 timestamps with explicit timezone (UTC preferred), e.g. ``"2026-05-15T16:30:00Z"``. Body fields (same schema as create…

Update an existing monitor's configuration.

Update a notification policy.

Update a resource group.

Update a secret's value by key.

Update a status page's name, slug, branding, visibility, or incident mode.

Update a status page component's name, group, or status.

Update a component group's name or display order.

Update a status page incident's title, impact, status, or components. Schedule fields belong on update_status_page_maintenance.

Update a maintenance window's title, impact, status, or schedule.

Update a tag.

Update a webhook endpoint.

Update a webhook testing inbox (name, status, mock reply, limits).

Re-check the TXT and MX records of a custom email testing domain.

Trigger DNS verification for a custom domain. Returns the updated domain with current verification status.

Wait up to ``wait_s`` seconds (max 25) for mail to a full address. Returns the oldest matching message, with extracted ``otp`` and ``links``. On timeout the tool errors; call it again or poll ``get_latest_email``. ``received_after`` is an ISO 8601 timestamp.

Wait up to ``wait_s`` seconds (max 25) for a request to an inbox. Returns the oldest matching event with headers and body (body capped at 64 KB). Filter with ``method`` and ``path_prefix``. On timeout the tool errors; call it again or poll ``get_latest_webhook_event``.