An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Hashicorp Nomad to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Control your cluster orchestration through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Nomad.

  1. 01

    Get job

    This capability retrieves the full configuration and current status for a specific Nomad job.

  2. 02

    Get node

    Use this to pull detailed information about a specific client node in your cluster.

  3. 03

    List allocations

    This capability provides a list of all currently running task allocations.

  4. 04

    List jobs

    This capability returns a list of all jobs registered within your Nomad cluster.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Nomad.

  1. 05

    List nodes

    Use this to see all client nodes currently participating in the cluster.

  2. 06

    Promote deployment

    This capability allows you to manually promote a deployment to continue a rollout.

  3. 07

    Fail deployment

    Use this to mark a deployment as failed, which triggers a rollback.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Nomad.

  1. 08

    Get allocation

    This capability fetches specific details for a single task allocation.

  2. 09

    Get deployment

    Use this to retrieve the status and details of a specific deployment.

  3. 10

    List deployments

    This capability lists the most recent deployments in your cluster.

Real work

What teams actually run

01

Rapid Health Checks

Ask your agent to check if any nodes are down during a scheduled maintenance window.

02

Deployment Monitoring

Watch the progress of a canary deployment by asking for recent deployment updates.

03

Automated Rollbacks

Tell your agent to fail a deployment if you notice errors in your application logs.

04

Resource Auditing

Request a list of all running allocations to verify workload distribution across nodes.

Automate a task

Put Nomad to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Nomad works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Nomad to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

940ms average. Fast in production.

Nomad is checked daily against the live service.

Daily averagePeak 1228ms
Oct 3Today
Fastest day
776ms
Slowest day
1228ms
14-day trend
Slowing+29%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Nomad, so you can see the experience inside your AI.

It does not authenticate your account with Nomad. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Nomad Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Nomad capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "hashicorp-nomad-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Nomad in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Nomad owners hand off.

This MCP is built for technical teams managing containerized workloads through Nomad orchestration.

  • 01

    DevOps Engineers

    They use the agent to check cluster health and job status without opening the Nomad UI.

  • 02

    SREs

    They hand off deployment tracking and rollback triggers to the agent during incidents.

  • 03

    Developers

    They monitor real-time task allocations and service deployment progress.

FAQ

Questions Nomad owners ask.

  • 01

    How do I connect this MCP to my Nomad cluster?

    You just need to provide your Nomad Address and your ACL Token in the Vinkius setup. Once connected, it's ready to use in any MCP-compatible client.

  • 02

    Can I trigger rollbacks using my AI agent?

    Yes. You can use the fail_deployment capability to mark a deployment as failed, which triggers a rollback in Nomad.

  • 03

    Which AI clients can use this Nomad MCP?

    It works with any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 04

    Does this MCP support monitoring node resources?

    Yes, you can use the agent to list nodes and retrieve detailed status and resource usage information.

  • 05

    Is my Nomad ACL token secure?

    Vinkius manages your credentials and keeps them secure while hosting the MCP for you.

  • 06

    How do I get my Nomad Address?

    Your Nomad Address is the URL where your Nomad server is reachable, usually including the port (e.g., http://nomad.example.com:4646).

  • 07

    Is an ACL Token required?

    Only if ACLs are enabled on your Nomad cluster. If enabled, you must provide a Secret ID with sufficient permissions to query the requested resources.

  • 08

    Can I use namespaces with this server?

    Yes! You can specify a target namespace in the authentication settings. The server will then filter all job and allocation queries to that specific namespace.

Explore

More in Loved By Devs

Suggestions

Connect Nomad to Claude, Cursor, ChatGPT & more