Nomad MCP Server

@kocierik

Basic information

About Nomad MCP Server

A nomad MCP Server (modelcontextprotocol)

Nomad MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "nomad-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@kocierik/mcp-nomad"
      ]
    }
  }
}

Nomad MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Nomad MCP Server?

A Golang-based MCP server that connects to HashiCorp Nomad, enabling Claude Desktop and other MCP clients to interact with Nomad resources such as jobs, allocations, and cluster information.

How to use Nomad MCP Server?

Install via npm (npx -y @kocierik/mcp-nomad), download a pre-built binary from GitHub Releases, or build from source with Go. Configure Claude Desktop by adding an entry to claude_desktop_config.json with the mcp-nomad command and environment variables (e.g., NOMAD_ADDR, NOMAD_TOKEN).

Key features of Nomad MCP Server

Supports stdio, SSE, and Streamable HTTP transports
Configurable via command-line flags and environment variables
Environment variables for Nomad address, token, region, namespace, and TLS
Pre-built npm package and binary releases for easy setup
MCP Inspector integration for local testing and debugging
Implements a clean interface-based tool architecture

Use cases of Nomad MCP Server

Monitor Nomad job status and allocation details from a chat interface
Manage Nomad clusters without leaving the Claude Desktop environment
Automate common Nomad operations using natural language commands
Explore Nomad resources and evaluate cluster health quickly

Frequently asked questions

What dependencies are required?

Node.js is needed only if using the npm-based installation. Pre-built binaries have no runtime dependencies. Building from source requires Go.

What environment variables must be set?

`NOMAD_ADDR` is required (default `http://localhost:4646`). `NOMAD_TOKEN` is optional for authenticated clusters. `NOMAD_REGION`, `NOMAD_NAMESPACE`, and TLS variables (`NOMAD_CACERT`, `NOMAD_SKIP_VERIFY`, `NOMAD_TLS_SERVER_NAME`) are also recognized.

How do I change the transport type?

Use the `-transport` flag (options: `stdio`, `sse`, `streamable-http`) when starting the server. Default is `stdio`.

Can I test the server before using it with Claude?

Yes – run `npx @modelcontextprotocol/inspector npx @kocierik/mcp-nomad` to launch the MCP Inspector connected to the server for debugging.

Does the server support TLS connections to Nomad?

Yes. Set the environment variables `NOMAD_CACERT`, `NOMAD_SKIP_VERIFY`, and `NOMAD_TLS_SERVER_NAME` to configure TLS for the Nomad HTTP client.

Comments

More Other MCP servers

Screenpipe

screenpipe

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

22.0K

Glasswarp

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.

Soar Flight Booking MCP

Soar Flight Booking MCP is a remote MCP server available at https://mcp.soar.flights.

Activepieces

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

23.2K

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.