Nomad MCP Server

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

FAQ from Nomad MCP Server

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.