helm-mcp
# helm-mcp
MCP server exposing the [HELM](https://github.com/dagamon/HELM) dashboard REST
API (`http://localhost:7010` by default) as tools for MCP clients.
## Tools
System: `helm_health`, `helm_system_info`, `helm_export`,
`helm_scheduler_next_runs`.
Services: `helm_list_services`, `helm_get_service`, `helm_start_service`,
`helm_stop_service`, `helm_restart_service`, `helm_service_logs`,
`helm_service_metrics`, `helm_create_service`, `helm_update_service`,
`helm_delete_service`.
Scripts: `helm_list_scripts`, `helm_get_script`, `helm_run_script`,
`helm_run_status`.
Service/script tools accept a numeric id **or** a name.
`POST /api/restart-server` is intentionally not exposed — the HELM process is
managed by NSSM/systemd and must not be restarted by the agent.
## Config
| Env var | Default | Meaning |
|------------|-------------------------|----------------------------------|
| `HELM_URL` | `http://localhost:7010` | HELM dashboard base URL |
| `HELM_PIN` | _(empty)_ | Dashboard PIN (sent as `x-pin`) |
## Run
```bash
uv sync
uv run helm-mcp # stdio transport
```
## Register with Claude Code
```bash
claude mcp add helm --scope user -- uv run --directory J:/dagamon_programs/mcp/helm-mcp helm-mcp
```
Add `--env HELM_PIN=<pin>` if `DASHBOARD_PIN` is set in HELM's `.env`.
TDQS
Scored across 35 tools
All 35 tools have clearly distinct purposes targeting specific resources and actions. There is no overlap between tools for services, stacks, scripts, themes, settings, docs, or system operations.
Tools follow a consistent 'verb_noun' pattern (e.g., helm_create_service, helm_list_docs), with only a few exceptions like helm_service_logs and helm_scheduler_next_runs that lack a verb prefix. The overwhelming majority are predictable.
35 tools is on the higher side but appropriate given the breadth of the domain: services, stacks, scripts, settings, themes, docs, updates, and diagnostics. Each tool earns its place without redundancy.
The tool surface covers CRUD and lifecycle operations for services and stacks, plus scripts and settings. Minor gaps exist: scripts lack create/update/delete, and settings lack a delete tool. Overall, the core workflows are well-supported.