helm-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@helm-mcplist all services"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
helm-mcp
MCP server exposing the 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.
Related MCP server: Enhanced MCP Server
Config
Env var | Default | Meaning |
|
| HELM dashboard base URL |
| (empty) | Dashboard PIN (sent as |
Run
uv sync
uv run helm-mcp # stdio transportRegister with Claude Code
claude mcp add helm --scope user -- uv run --directory J:/dagamon_programs/mcp/helm-mcp helm-mcpAdd --env HELM_PIN=<pin> if DASHBOARD_PIN is set in HELM's .env.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dagamon/HELM-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server