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).

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.

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.

HashiCorp Nomad MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: HashiCorp Nomad
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install HashiCorp Nomad and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "hashicorp-nomad": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About HashiCorp Nomad MCP Server

Connect your HashiCorp Nomad cluster to your AI agent and take control of your orchestration and workload management through natural conversation.

GitHub Copilot Agent mode brings HashiCorp Nomad data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Job Oversight — List all registered jobs and fetch their complete configuration and current status.
Cluster Health — Monitor active client nodes and retrieve detailed resource usage and status info.
Deployment Tracking — Follow the progress of rolling updates and manage canary deployments.
Workload Management — List all running instances (allocations) and inspect specific task details.
Operational Control — Manually promote successful deployments or fail underperforming ones to trigger rollbacks.
Deep Inspection — Fetch complete metadata for specific jobs, nodes, or allocations using their unique IDs.

The HashiCorp Nomad MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect HashiCorp Nomad to VS Code Copilot via MCP

Follow these steps to integrate the HashiCorp Nomad MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using HashiCorp Nomad

Ask Copilot: "Using HashiCorp Nomad, help me...". 10 tools available

Why Use VS Code Copilot with the HashiCorp Nomad MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with HashiCorp Nomad through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

HashiCorp Nomad + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the HashiCorp Nomad MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

HashiCorp Nomad MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect HashiCorp Nomad to VS Code Copilot via MCP:

fail_deployment

Mark a deployment as failed

get_allocation

Get specific allocation details

get_deployment

Get specific deployment details

get_job

Get specific job details

get_node

Get specific node info

list_allocations

List all task allocations

list_deployments

List recent deployments

list_jobs

List all Nomad jobs

list_nodes

List all client nodes

promote_deployment

Promote a deployment

Example Prompts for HashiCorp Nomad in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with HashiCorp Nomad immediately.

"List all active jobs in the 'production' namespace."

"Check the status of all client nodes in the cluster."

"Promote the deployment with ID 'dep-98765'."

Troubleshooting HashiCorp Nomad MCP Server with VS Code Copilot

Common issues when connecting HashiCorp Nomad to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

HashiCorp Nomad + VS Code Copilot FAQ

Common questions about integrating HashiCorp Nomad MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.