Nomad Connector for AI agents.
10 live capabilities
Manage cluster workloads and job orchestration through a conversational interface.
Waiting for input…
Why people use Nomad
HashiCorp Nomad Cluster Orchestration Management
With this Connector, you just ask your agent for the status of your production jobs. It pulls the data from your cluster and gives you a clear summary in seconds. You get a direct line to your infrastructure that lets you act on problems without the manual overhead.
What Vinkius changes
You get a conversational interface for your entire Nomad cluster.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 5,900+ Connectors
- Real-world use case 01
Stalled deployment troubleshooting
An SRE asks the agent to list_deployments to see where an update stalled, then uses get_deployment to find the error.
- Real-world use case 02
Rapid cluster health checks
An admin asks the agent to list_nodes to see if any servers are offline during a heavy traffic spike.
- Real-world use case 03
Canary promotion
A developer sees a successful canary and tells the agent to promote_deployment to roll it out to the whole cluster.
Complete set · 10capabilities
The complete Nomad capability set.
These are the exact actions your AI can choose when you ask it to work with Nomad.
01—04
4 capabilities in this set.
Part of 10 available through Nomad.
- 01 Capability
Get deployment
Fetch the specific details and status of a deployment. This is useful for checking the progress of a rolling update.
- 02 Capability
Get job
Pull the complete configuration and status for a specific job. Use this to see the exact parameters of a running service.
- 03 Capability
Get node
Get the current status and resource info for a specific client node. This helps you troubleshoot individual server issues.
- 04 Capability
List allocations
See a list of all task allocations currently running in your cluster. Use this to get a bird's eye view of active workloads.
05—07
3 capabilities in this set.
Part of 10 available through Nomad.
- 05 Capability
List deployments
See a list of your most recent deployments. This lets you quickly track the history of your recent rollout attempts.
- 06 Capability
List jobs
List every job currently registered in your Nomad cluster. Use this to see what's currently scheduled to run.
- 07 Capability
List nodes
See a list of all client nodes in your cluster. This is your first stop for checking cluster-wide health.
08—10
3 capabilities in this set.
Part of 10 available through Nomad.
- 08 Capability
Promote deployment
Manually promote a successful deployment to the next stage. This is great for moving through canary deployment phases.
- 09 Capability
Fail deployment
Mark a specific deployment as failed to trigger a rollback. Use this when an update goes wrong and you need to stop it.
- 10 Capability
Get allocation
Retrieve the specific details for a single task allocation. This helps you see exactly what a specific task is doing.
Set up in minutes
One URL. Then ask Nomad to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Nomad from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Nomad, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Nomad for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Nomad URL.
- Step 03
Save and start
Save the connection and enable Nomad in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"hashicorp-nomad": {
"url": "https://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp"
}
}
} - Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Nomad
Open Agent mode in chat and ask: "Using Nomad, help me...". 10 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"hashicorp-nomad": {
"url": "https://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp"
}
}
} - Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Nomad
Ask Copilot: "Using Nomad, help me...". 10 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"hashicorp-nomad": {
"url": "https://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp"
}
}
} - Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Nomad
Open Cascade and ask: "Using Nomad, help me...". 10 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"hashicorp-nomad": {
"url": "https://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp"
}
}
} - Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Nomad
Ask Cline: "Using Nomad, help me...". 10 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add hashicorp-nomad --transport http "https://edge.vinkius.com/vk_preview_HSllBsK0lF7lUrIFLAuIb4teHoynOaI9ff1XV1bj/mcp" - Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Nomad
Ask Claude: "Using Nomad, show me...". 10 tools are ready
Where the request belongs
Work Nomad can move forward.
This is for the person who manages production workloads and needs to know what's happening right now without clicking through five different pages.
SRE Engineer
Checking if the production cluster is healthy at 3 AM without needing to log into a VPN or UI.
DevOps Engineer
Tracking rolling updates and canary deployments to ensure they didn't stall.
Infrastructure Manager
Pulling node and workload data to build reports for the leadership team.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsRancher
Equip your AI to manage Kubernetes environments directly through Rancher, overseeing clusters, namespaces, and active pods.
Flystack
Manage cloud infrastructure. audit deployments, clusters, and metrics via AI.
Qovery
Bring effortless Kubernetes and cloud deployment management to your IDE. List environments, check application states, restart pods, and deploy exact Git commits via chat.
Argo CD (GitOps)
Manage Kubernetes deployments via Argo CD. sync applications, check logs, and manage clusters/repositories directly from your AI agent.
Cloudify
Orchestrate cloud infrastructure via Cloudify. manage blueprints, deployments, and monitor workflow executions directly from any AI agent.
Argo Workflows
Automate Kubernetes orchestrations via Argo Workflows. monitor, list, and inspect active pods, crons, and workflow templates directly from any AI agent.
Bring your own AI
Change the model, client or framework. Keep Nomad connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Nomad.
The practical details behind the request, access and result.
Can I use the HashiCorp Nomad MCP to check my cluster health?
Yes, it lets you see which nodes are up or down in real time. You can quickly identify hardware issues or connectivity problems without opening a dashboard.
How does the HashiCorp Nomad MCP help with deployments?
It lets you track rolling updates and manually promote or fail them. This makes managing canary releases and rollbacks much faster and less error-prone.
Does the HashiCorp Nomad MCP support multi-region clusters?
It connects to your specific Nomad address to pull data from your cluster. Whether that cluster is local or spread across regions depends on your own setup.
Can I use this to see my job configurations?
Yes, you can fetch the full configuration for any registered job. This is great for verifying that your agent-managed updates actually applied the correct settings.
Is the HashiCorp Nomad MCP good for SRE teams?
It's built for SREs who need to quickly check statuses without opening the UI. It provides a fast way to get the facts during an incident.
Can I use the HashiCorp Nomad MCP to manage my workloads?
Yes, you can list all running allocations and inspect task details. It gives you a way to interact with your active workloads using natural language.
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.
One connection away
Give your agent a direct line to Nomad.
Connect Nomad once. Keep it beside 5,900+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available