# Devhelmhq MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.devhelmhq%2Fmcp-server
Registry id: `mcp-registry/io.github.devhelmhq/mcp-server`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "devhelmhq-mcp-server": {
      "command": "uvx",
      "args": [
        "devhelm-mcp-server"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add devhelmhq-mcp-server -- uvx devhelm-mcp-server
```

## Tools (80)

- `acquire_deploy_lock`: Acquire a deploy lock to prevent concurrent deployments. Required: lockedBy (identity of requester, e.g. hostname or CI job ID). Optional: ttlMinutes (default 3
- `add_resource_group_member`: Add a monitor to a resource group. Required fields: monitorId.
- `cancel_maintenance_window`: Cancel a maintenance window — alerts resume immediately. Call this AFTER a deploy or maintenance operation completes successfully so any new monitor failures su
- `create_alert_channel`: Create a new alert channel. Required: name, type, config (type-specific). Types: EMAIL, WEBHOOK, SLACK, PAGERDUTY, OPSGENIE, TEAMS, DISCORD, TELEGRAM, GOOGLE_CH
- `create_api_key`: Create a new API key. The key value is returned only once. Required fields: name. Optional: expiresAt.
- `create_environment`: Create an environment. Required fields: name, slug, color.
- `create_incident`: Create a manual incident. Required fields: title, severity (DOWN/DEGRADED/MAINTENANCE). Optional: monitorId (UUID), body (detailed description).
- `create_maintenance_window`
- `create_monitor`
- `create_notification_policy`: Create a notification policy. Required: name, matchRules (list of {type, value?, monitorIds?, regions?}), escalation ({steps: [{delayMinutes, channelIds}], onRe
- `create_resource_group`: Create a resource group. Required fields: name. Optional: description.
- `create_secret`: 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}}.
- `delete_alert_channel`: Delete an alert channel.
- `delete_api_key`: Delete an API key permanently.
- `delete_dependency`: Stop tracking a service dependency.
- `delete_environment`: Delete an environment by slug.
- `delete_monitor`: Delete a monitor permanently.
- `delete_notification_policy`: Delete a notification policy.
- `delete_resource_group`: Delete a resource group.
- `delete_secret`: Delete a secret by key.
- `force_release_deploy_lock`: Force-release any active deploy lock (admin action).
- `get_alert_channel`: Get an alert channel by ID.
- `get_all_components_uptime`: 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
- `get_api_key`: Get a single API key's metadata by id. The secret value is never returned.
- `get_check_trace`: 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)
- `get_component_uptime`: 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 
- `get_current_deploy_lock`: Get the currently active deploy lock, or null if unlocked.
- `get_dependency`: Get a tracked dependency by ID.
- `get_environment`: Get an environment by slug (e.g. 'production', 'staging').
- `get_incident`: Get a single incident by ID with full details.
- `get_incident_timeline`: Full forensic timeline for an incident. Returns every recorded state transition for the incident, the rule evaluations that caused each triggering transition, a
- `get_maintenance_window`: Get a single maintenance window by ID with full details.
- `get_monitor`: Get a single monitor by ID, including its full configuration.
- `get_notification_policy`: Get a notification policy by ID.
- `get_policy_snapshot`: 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 tr
- `get_resource_group`: Get a resource group by ID.
- `get_service`: Get a catalog service's summary by slug (e.g. 'github'), including its current status, categories, and component overview.
- `get_service_day_rollup`: 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 overl
- `get_service_incident`: Get one vendor incident in full detail, including the vendor's timeline of status updates (investigating → identified → resolved). Get incident IDs from list_se
- `get_service_live_status`: 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
- `get_service_uptime`: Get historical uptime stats for a catalog service over a period (e.g. '7d', '30d', '90d'; default '30d').
- `get_services_summary`: Get the global status summary across the entire service catalog — counts of operational / degraded / outage services. Use this for a quick 'is anything broken o
- `get_status_overview`: Get the dashboard overview with monitor counts, incident summary, and uptime stats.
- `list_alert_channels`: List all alert channels configured in the workspace.
- `list_api_keys`: List all API keys in the workspace.
- `list_dependencies`: List all tracked service dependencies.
- `list_environments`: List all environments in the workspace.
- `list_incidents`: List all incidents in the workspace.
- `list_maintenance_windows`
- `list_monitor_results`: List recent check results for a monitor (cursor-paginated).
- `list_monitor_rule_evaluations`: List rule evaluations produced for a monitor (paginated). Filters: - rule_type: e.g. "consecutive_failures", "latency_threshold" - region: probe region, e.g. "u
- `list_monitor_transitions`: List state transitions recorded for a monitor (paginated). A transition captures every WATCHING→TRIGGERED→CONFIRMED→RESOLVED edge the detection engine walked. I
- `list_monitor_versions`: List version history for a monitor.
- `list_monitors`: List all uptime monitors in the workspace.
- `list_notification_policies`: List all notification policies in the workspace.
- `list_resource_groups`: List all resource groups in the workspace.
- `list_secrets`: List all secrets (metadata only, values are never returned).
- `list_service_categories`: List all service catalog categories (e.g. cloud, payments, devtools) usable as the `category` filter in search_services.
- `list_service_components`: 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 
- `list_service_incidents`: 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 'wh
- `list_service_maintenances`: List scheduled and past maintenance windows announced by a catalog service (e.g. upcoming AWS maintenance that could affect you).
- `pause_monitor`: Pause a monitor (stops checking until resumed).
- `release_deploy_lock`: Release a deploy lock by ID.
- `remove_resource_group_member`: Remove a monitor from a resource group.
- `resolve_incident`: Resolve an active incident, optionally with a resolution message.
- `resume_monitor`: Resume a paused monitor.
- `revoke_api_key`: Revoke an API key (disables it without deleting).
- `search_services`: 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. 'strip
- `test_alert_channel`: Send a test notification to an alert channel to verify it works.
- `test_monitor`: Trigger an ad-hoc test run for a monitor and return the result.
- `test_notification_policy`: Send a test dispatch to verify a notification policy's routing.
- `track_dependency`: 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
- `update_alert_channel`: Update an existing alert channel. Updatable fields: name, type, config (type-specific). See create_alert_channel for supported types.
- `update_dependency_alert_sensitivity`: Change how loudly a tracked dependency alerts you. Levels: AWARENESS (silent tracking, default — status visible on the dashboard but no notifications), INCIDENT
- `update_environment`: Update an environment by slug.
- `update_maintenance_window`
- `update_monitor`: Update an existing monitor's configuration.
- `update_notification_policy`: Update a notification policy.
- `update_resource_group`: Update a resource group.
- `update_secret`: Update a secret's value by key.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.