MCP Nomad MCP Server

<h4 align="center">Golang-based MCP server connecting to Nomad</h4>

Local serverstdioGo

What is the MCP Nomad MCP server?

MCP Nomad MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Golang-based MCP server connecting to Nomad.

What the assistant can call

Once MCP Nomad is connected, these are the calls the assistant has available:

  • NOMAD_ADDR — Nomad HTTP API address (default: http://localhost:4646)
  • NOMAD_TOKEN — Nomad ACL token (optional)
  • NOMAD_REGION — forwarded as the REST region query parameter when callers do not override it (multi-region clusters)
  • NOMAD_NAMESPACE — default namespace for tools that accept an optional namespace when the tool omits it
  • TLS — NOMAD_CACERT, NOMAD_SKIP_VERIFY, NOMAD_TLS_SERVER_NAME (see utils/client.go / buildTLSConfig)
  • Prerequisite — Node.js

Configuration and credentials

You will need 3 environment variables: NOMAD_TOKEN, NOMAD_ADDR, NOMAD_REGION. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

@kocierik/mcp-nomad on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Nomad's toolset — NOMAD_ADDR, NOMAD_TOKEN, NOMAD_REGION and 3 more — is a fair guide to whether it matches your workflow. It is maintained by kocierik; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp nomad mcp server does with a few real requests.

Available tools

ToolWhat it does
NOMAD_ADDRNomad HTTP API address (default: http://localhost:4646)
NOMAD_TOKENNomad ACL token (optional)
NOMAD_REGIONforwarded as the REST region query parameter when callers do not override it (multi-region clusters)
NOMAD_NAMESPACEdefault namespace for tools that accept an optional namespace when the tool omits it
TLSNOMAD_CACERT, NOMAD_SKIP_VERIFY, NOMAD_TLS_SERVER_NAME (see utils/client.go / buildTLSConfig)
PrerequisiteNode.js

How to install the MCP Nomad MCP server

{
  "mcpServers": {
    "nomad": {
      "command": "npx",
      "args": ["-y", "@kocierik/mcp-nomad"],
      "env": {
        "NOMAD_TOKEN": "your-value",
        "NOMAD_ADDR": "your-value",
        "NOMAD_REGION": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
NOMAD_TOKENCredential the server authenticates with.Yes
NOMAD_ADDRConfiguration value read at startup.Optional
NOMAD_REGIONConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP Nomad to NOMAD ADDR.
  • Use MCP Nomad to NOMAD TOKEN.
  • Use MCP Nomad to NOMAD REGION.

Frequently asked questions

It connects MCP Nomad to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (NOMAD_ADDR, NOMAD_TOKEN, NOMAD_REGION, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Nomad directly.