Skip to main content
The DevHelm MCP server exposes 128 tools across 17 categories. Authentication is handled at the transport layer (Bearer header or env var) — api_token is accepted as a back-compat parameter on every tool but is hidden from LLM-facing schemas to prevent token leakage.

Monitors (10 tools)

Incidents (4 tools)

Incidents cannot be deleted — only resolved. Once resolved, they remain in history for audit and reporting.

Alert channels (6 tools)

Notification policies (6 tools)

Environments (5 tools)

Secrets (4 tools)

Tags (5 tools)

Resource groups (7 tools)

Webhooks (6 tools)

API keys (4 tools)

Dependencies (5 tools)

Deploy lock (4 tools)

Status (1 tool)

Forensics (5 tools)

Read-only audit trail for the detection engine — incident timelines, check traces, policy snapshots, rule evaluations, and state transitions. See Incident Forensics for the conceptual overview.

Status pages (38 tools)

The largest category — covers the full status page surface: pages, components, groups, incidents, maintenance, subscribers, and custom domains.

Pages

Components

Groups

Incidents

Maintenance

Customer-facing scheduled notices on the public status page: title, impact, and window. Mute alerts with create_maintenance_window. Vendor catalog windows are list_service_maintenances.

Subscribers

Custom domains

Services (13 tools)

Browse the third-party service catalog — search services, check live status, pull uptime history, list vendor incidents and maintenance windows.

Maintenance windows (5 tools)

Schedule downtime to suppress alerts during planned work (deploys, migrations, vendor maintenance).

Body parameter format

Tools that accept a body parameter expect a JSON object matching the corresponding REST API request schema. Refer to the API Reference for field-level details.

Next steps

MCP configuration

Transport modes and client setup.

API Reference

REST API schemas for body parameters.