DevHelm MCP Server

io.github.devhelmhqPublished by GitHub account devhelmhqv1.0.2Updated Oct 24, 2026

Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant manage DevHelm uptime monitors, incidents, alerting, dependencies, and status pages through the DevHelm API.

What you can do
Connects an AI coding assistant to a DevHelm account so it can list, create, update, pause, resume, test, and delete uptime monitors, and read their results and versions. It also covers incidents, alert channels, notification policies, environments, secrets, tags, resource groups, webhooks, API keys, dependencies, deploy locks, and status pages. Tools are grouped by category, for example Monitors, Incidents, Alert Channels, and Status Pages.
When to use it
Useful when you want an assistant to inspect or change monitoring configuration without leaving the editor: checking monitor status and results, opening or resolving incidents, adjusting alert channels and notification policies, or reviewing dependencies and status pages.
Requirements
Runs locally over stdio via the PyPI package devhelm-mcp-server, started with uvx or after pip install, and needs a DevHelm API token in the DEVHELM_API_TOKEN environment variable. The README also documents a hosted endpoint at mcp.devhelm.io using bearer auth or a token embedded in the URL. Network access to DevHelm is required.
Before you install
The token in DEVHELM_API_TOKEN grants access to the DevHelm account, and the README's URL form places that token directly in the endpoint URL, where it may be stored in client configuration or logs. Many tools write: monitors, incidents, alert channels, notification policies, environments, secrets, tags, resource groups, webhooks, and API keys can be created, updated, or deleted, and deploy locks can be force-released. API key tools can create and revoke credentials.

Installation

In SourceWeft

  1. Open DevHelm MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

DevHelm MCP Server

Model Context Protocol (MCP) server for DevHelm — gives AI coding assistants (Cursor, Claude Desktop, Windsurf, etc.) access to your uptime monitors, incidents, alerting, and more.

Quick Start

Hosted (recommended)

Use the hosted server at mcp.devhelm.io. Two connection modes:

Bearer auth:

URL: https://mcp.devhelm.io/mcpAuthorization: Bearer <your-api-token>

API key in URL (for clients that only accept a URL):

URL: https://mcp.devhelm.io/<your-api-token>/mcp

Local (stdio)

bash
pip install devhelm-mcp-serverexport DEVHELM_API_TOKEN=your-tokendevhelm-mcp-server

Or with uvx (no install required):

bash
export DEVHELM_API_TOKEN=your-tokenuvx devhelm-mcp-server

Cursor / Claude Desktop

Add to your MCP config:

json
{  "mcpServers": {    "devhelm": {      "url": "https://mcp.devhelm.io/<your-api-token>/mcp"    }  }}

Available Tools

CategoryTools
Monitorslist, get, create, update (inline code for BROWSER / MULTI_STEP_API), delete (confirmation), restore, trash, pause, resume, mute, unmute, quarantine, release quarantine, drift, versions, history (list_monitor_results is a deprecated alias until 2027-01-31)
Code checkstest, probe, test ad hoc, run now, trigger; revisions list, get, files, create draft, test, diff, discard; publish and rollback (confirmation), rollback preview
Runsget (run envelope, wait_s ≤ 25), list, steps, console, network, artifacts (screenshots as images, traces/HARs as signed URLs), trace summary, diff, cancel
Accountruntimes list/get, usage, entitlements
Incidentslist, get, create, update, acknowledge, add update, resolve, runs, events, related, trigger; prompt investigate_incident
Alert Channelslist, get, create, update, delete, test
Notification Policieslist, get, create, update, delete, test
Environmentslist, get, create, update, delete
Secretslist, set value, create, update (values via elicitation or a dashboard link, never in chat), delete
Tagslist, get, create, update, delete
Resource Groupslist, get, create, update, delete, add member, remove member
Webhookslist, get, create, update, delete, test
API Keyslist, create, revoke, delete
Dependencieslist, get, track, delete
Deploy Lockacquire, current, release, force-release
Statusoverview
Status Pagespages, components, groups, incidents, maintenance, subscribers, domains
Email Testingcreate address, wait (≤25 s), latest, list/get messages, source, OTP codes, links, inject; domains list, get, create, update, verify, activity
Webhook Testinginboxes list, get, create, update, activity; wait (≤25 s), latest, list/get events

Delete, publish and rollback return {status: "confirmation_required", changes, confirmationToken} first; call again with confirmation_token after the user agrees. Tokens are HMACs signed by the server process (set DEVHELM_MCP_CONFIRMATION_SECRET so every replica shares the key) and last 15 minutes. Errors come back as isError with every ErrorResponse field and a sentence for the agent.

Development

bash
uv syncmake dev          # Start with MCP Inspector (stdio)make serve        # Start HTTP server on :8000make test         # Run unit testsmake lint         # Check formattingmake typecheck    # Run mypy

License

MIT

Source: README.md at commit 20f5b59

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts