Kai
Run a Kubernetes cluster from an assistant — workloads, networking, config, storage, RBAC, CRDs and raw manifests.Read full description
basebanditLABSCO SUMMARY
A typed bridge to Nomad, not a shell wrapper around the CLI.
Tools sit behind narrow interfaces and the generic request helper refuses any path outside an internal allow-list, so an agent cannot wander the whole API surface. Before wiring it into a client, run it under the MCP Inspector — npx @modelcontextprotocol/inspector npx @kocierik/mcp-nomad — and look at the tool list it registers.
What it is
A single Go binary that connects an MCP client to a Nomad cluster. It speaks Nomad's official /v1/ API rather than shelling out to the CLI, and ships as an npm package, a release binary, or a go install target.
What you get
- Cluster access from the conversation, over the same /v1/ API the Nomad CLI uses
- Typed helpers for cluster actions, including stopping an allocation
- Three transports: stdio by default, plus sse and streamable-http on a port you choose
- Region and namespace defaults, so calls that omit them still land in the right place
- A path allow-list on the generic request helper, which rejects API paths outside it
Requirements
NOMAD_ADDR for the cluster address, default http://localhost:4646, and NOMAD_TOKEN if your cluster uses ACLs. TLS is configured with NOMAD_CACERT, NOMAD_SKIP_VERIFY and NOMAD_TLS_SERVER_NAME. Node is needed only for the npx path; the release binary needs nothing, and building from source needs Go.
Setup effort
One command — npx -y @kocierik/mcp-nomad
USE CASES
01
Checking cluster state without opening the Nomad UI
Ask about jobs and allocations in the conversation; answers come from the same /v1/ API the CLI reads.
02
Stopping a stuck allocation
Use the typed stop helper rather than hand-crafting a raw API path, which the allow-list would reject anyway.
03
Working across regions and namespaces
Set NOMAD_REGION and NOMAD_NAMESPACE once; calls that leave them unset fall back to those defaults.
04
Seeing what it exposes before you trust it
Attach the MCP Inspector to the published build and browse the registered tools first.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @kocierik/mcp-nomadMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp_nomad": {
"command": "npx",
"args": [
"-y",
"@kocierik/mcp-nomad"
],
"env": {
"NOMAD_TOKEN": "<YOUR_NOMAD_TOKEN>",
"NOMAD_ADDR": "<YOUR_NOMAD_ADDR>"
}
}
}
}
