Skip to main content
Glama
dagamon

helm-mcp

by dagamon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to helm-mcp

No user-submitted related servers found.

    Related Servers

    • jakubs-mcp-tools

      Jakub2841
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for infrastructure discovery and remote management, enabling SSH command execution, file transfer, log tailing, and machine/service inventory with a companion web dashboard.
      2
      -

    • pi-mcp

      Lukewtye
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Raspberry Pi exposing tools for host health checks, shell execution, and Docker container restarts over authenticated HTTP.
      1
      -

    • komodo-mcp

      digital-grease
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that exposes the full API of the Komodo infrastructure management platform. It enables users to manage deployments, stacks, servers, and containers through tools for inspection, configuration, and operational control.
      MIT

    • MCP Tools Hub

      lapaduga
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server with a web interface for viewing and calling tools via REST API, enabling easy tool management through a browser.
      -

    • mcp-infra

      DerWolk
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for filesystem, database, web, system, and shell operations, along with resources and prompts via SSE transport.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 35 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources