Skip to main content
Glama
udaisingh93

nomad-mcp

by udaisingh93
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to nomad-mcp

No user-submitted related servers found.

    Related Servers

    • iowap-mcp

      iowap-org
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP-speaking AI agent to use a curated toolset over the node CLI for relay health, fleet and capability discovery, task submission and result polling, artifact downloads, and live documentation, without handling credentials directly.
      MIT

    • proxmox-mcp

      ManciDRaffy
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to monitor and manage a Proxmox VE cluster, including cluster status, VM/container lifecycle, and node actions via MCP tools.
      8
      MIT
    • Scout MCP Server by scoutos-labs

      Scout MCP Serverofficial

      scoutos-labs
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Scout Live platform capabilities through standardized MCP primitives, including tools for app management, deployment, and logging.
      6
      12 npm
      MIT

    • ha-automation-mcp

      aderik
      A
      license
      B
      quality
      F
      maintenance
      Exposes the Home Assistant Automation API integration as MCP tools so an AI agent can manage automations, helpers and template entities, Lovelace dashboards, entity/device/config-entry registries, recorder history, and native entity state and service calls without hand-editing YAML.
      58
      MIT
    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 12 tools

    Disambiguation5/5

    Every tool maps to a distinct resource and scope, with list_ and get_ clearly separating collection vs single-detail operations. Potentially similar tools like get_job_deployments and list_deployments are disambiguated by job-scoped vs cluster-scoped descriptions.

    Naming Consistency5/5

    All tools follow a consistent list_/get_ + resource noun pattern in snake_case. Singular resources use get_, plural resources use list_, and job-scoped variants like get_job_allocations are predictable.

    Tool Count5/5

    Twelve tools provide well-scoped coverage of Nomad's main observable resources: jobs, allocations, deployments, nodes, and namespaces. There is no obvious redundancy, and each tool serves a distinct inspection or diagnostic purpose.

    Completeness4/5

    As a read-only observability toolset, it covers the key Nomad resources needed for inspecting jobs, allocations, deployments, evalutions, and nodes. Minor gaps like no cluster-wide allocation list, no single evaluation detail, and no write/lifecycle operations prevent a perfect score if full Nomad management is expected.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources