DevHelm MCP Server
Monitor uptime, manage incidents, configure alerting, and query third-party dependency status through DevHelm's monitoring platform
MCP Server
Give your AI coding assistant access to DevHelm monitors, incidents, alerting, status pages, and more — in one line of config
The DevHelm MCP server gives AI coding assistants like Cursor, Claude Desktop, and Windsurf direct access to your monitoring stack. Create monitors, investigate incidents, manage alert channels, and configure status pages — all through natural language in your editor.
DevHelm hosts the server at mcp.devhelm.io so there's nothing to install. Add the URL to your MCP client config and you're connected.
Connect in 30 seconds
All you need is your API token and one config entry. Grab a token from Settings → API Keys in the Dashboard.
Add to `.cursor/mcp.json` in your project root (or `~/.cursor/mcp.json` for global access):```json theme={null}
{
"mcpServers": {
"devhelm": {
"url": "https://mcp.devhelm.io/mcp",
"headers": {
"Authorization": "Bearer dh_live_xxxxxxxx"
}
}
}
}
```
Add to your Claude Desktop config:
* **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
```json theme={null}
{
"mcpServers": {
"devhelm": {
"url": "https://mcp.devhelm.io/mcp",
"headers": {
"Authorization": "Bearer dh_live_xxxxxxxx"
}
}
}
}
```
Add to your Windsurf MCP settings:
```json theme={null}
{
"mcpServers": {
"devhelm": {
"url": "https://mcp.devhelm.io/mcp",
"headers": {
"Authorization": "Bearer dh_live_xxxxxxxx"
}
}
}
}
```
Any MCP-compatible client that supports Streamable HTTP can connect to the hosted server.
**If your client supports custom headers** (recommended):
```
URL: https://mcp.devhelm.io/mcp
Header: Authorization: Bearer dh_live_xxxxxxxx
```
**If your client only accepts a URL** (token in path):
```
URL: https://mcp.devhelm.io/dh_live_xxxxxxxx/mcp
```
<Warning>
The path-based form embeds your token in the URL. Treat the entire URL as a secret — don't commit it to a public repo. Prefer the header form whenever possible.
</Warning>
That's it. Restart your MCP client and the DevHelm tools will appear.
What you can do
Once connected, talk to your assistant like you would to a teammate:
- "List all my monitors and their current status" — get a quick overview without leaving your editor
- "Create an HTTP monitor for api.example.com/health checking every 60 seconds from us-east" — spin up monitoring in seconds
- "Show me active incidents and the recent check results for the failing one" — investigate without context-switching to the dashboard
- "Set up a Slack alert channel with this webhook URL" — wire up notifications conversationally
- "Add api.example.com as a component on the public status page" — manage your status page from chat
- "What's the uptime for the payments service over the last 30 days?" — pull reporting data inline
The MCP server covers the entire DevHelm product surface — anything you can do in the dashboard or CLI, your AI assistant can do too.
Available tools
The server exposes over 100 tools across 15 categories:
| Category | Tools |
|---|---|
| Monitors | list, get, create, update, delete, pause, resume, test, results, versions |
| Incidents | list, get, create, resolve |
| Alert channels | list, get, create, update, delete, test |
| Notification policies | list, get, create, update, delete, test |
| Resource groups | list, get, create, update, delete, add/remove members |
| Tags | list, get, create, update, delete |
| Environments | list, get, create, update, delete |
| Secrets | list, get, create, update, delete |
| API keys | list, get, create, revoke |
| Webhooks | list, get, create, update, delete, test |
| Status pages | list, get, create, update, delete, components, groups, incidents, subscribers, domains |
| Forensics | incident timeline, check trace, policy snapshot, rule evaluations, transitions |
| Dependencies | list, get, track, delete |
| Deploy lock | acquire, current, release, force-release |
| Status / health | overview |
See the Tools reference for the full per-tool catalog with parameters.
Alternative: run locally
If you prefer to run the server on your own machine (offline use, air-gapped environments, or development), the same code is published to PyPI as devhelm-mcp-server. It speaks MCP over stdio.
uvx devhelm-mcp-server
See Configuration → Run locally for full local setup instructions and per-client config snippets.
Next steps
Authentication modes, environment variables, local setup, and troubleshooting. Full per-tool catalog with parameters and return shapes.Servidores relacionados
Alpha Vantage MCP Server
patrocinadorAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
Tox Testing
Executes tox commands to run Python tests with pytest. Requires the TOX_APP_DIR environment variable to be set.
ejentum-mcp
Reasoning Harness for agentic AI: 4 cognitive modes (reasoning, code, anti-deception, memory), 679 engineered abilities served as MCP tools, runtime scaffold injection.
Puppeteer MCP
MCP server for browser automation via Puppeteer
SeaLights
An MCP server for interacting with the SeaLights platform for quality intelligence.
Kitsune MCP
Shape-shifting MCP hub — shapeshift() into 10,000+ servers at runtime. One entry point, no restarts, 7 registries.
Neural memory
A memory for AI, without cloud service or fee, everything local (Most useful for coding)
Debugg AI
Enable your code gen agents to create & run 0-config end-to-end tests against new code changes in remote browsers via the Debugg AI testing platform.
Kirby MCP
CLI-first MCP server for composer-based Kirby CMS projects—inspect blueprints/templates/plugins, interact with a real Kirby runtime, and use a bundled Kirby knowledge base.
JADX-AI-MCP
A JADX decompiler plugin that integrates with MCP to provide live reverse engineering support using LLMs.
ForgeCraft
MCP server that generates production-grade engineering standards (SOLID, testing, architecture, CI/CD) for AI coding assistants