How to Use the HashiCorp Nomad MCP in CrewAI

Q: How do I configure CrewAI to use the HashiCorp Nomad MCP Server?

Install crewai and pass the Vinkius server URL directly in your Agent's mcps list. For advanced setups, use MCPServerHTTP to filter which tools are exposed to specific agents. This lets you restrict sensitive tools like faildeployment to your operator agent.

Q: How can my crew inspect active job files?

Your agents call getjob to retrieve the raw configuration for any active workload. Your research agent can read this file to understand the environment variables and volume mounts. It helps your crew suggest configuration fixes when tasks fail to start.

Run cooperative agent squads to monitor and repair HashiCorp Nomad clusters using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect HashiCorp Nomad MCP to CrewAI

Create your Vinkius account to connect HashiCorp Nomad to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup HashiCorp Nomad with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate rollouts with specialized CrewAI agents

`list_deployments` provides a history of recent job rollouts across the cluster. A specialized monitor agent watches this list to detect new canary deployments. When a new deployment appears, the agent passes the deployment ID to a validator agent. That validator uses `get_deployment` to track the health of the active canary allocations.

Resolve allocation failures with an MCP Server crew

`list_allocations` displays the state of every task group running on your client nodes. An incident response crew queries this endpoint when alerts trigger. If an allocation crashes, the crew uses `get_allocation` to inspect the exit codes and logs. The agents then decide whether to trigger a rollback or notify the on-call engineer.

Analyze node health with autonomous agents

`list_nodes` lists all active client machines in your scheduling pool. A capacity planning agent reviews this list to identify resource bottlenecks via the MCP client. By calling `get_node`, the agent inspects CPU and memory allocations on individual machines. This lets your crew draft scaling recommendations or schedule maintenance windows.

Setup guide

Set up HashiCorp Nomad MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke HashiCorp Nomad tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="HashiCorp Nomad Analyst",
    goal="Access and analyze HashiCorp Nomad data via MCP.",
    backstory="Expert analyst with direct HashiCorp Nomad access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent HashiCorp Nomad transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="HashiCorp Nomad Analyst",
        goal="Access and analyze HashiCorp Nomad data via MCP.",
        backstory="Expert analyst with direct HashiCorp Nomad access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent HashiCorp Nomad transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Nomad. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect HashiCorp Nomad now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about HashiCorp Nomad MCP in CrewAI

Install `crewai` and pass the Vinkius server URL directly in your Agent's `mcps` list. For advanced setups, use `MCPServerHTTP` to filter which tools are exposed to specific agents. This lets you restrict sensitive tools like `fail_deployment` to your operator agent.

Yes, CrewAI agents use shared memory to pass task outputs like deployment IDs between each other. A monitor agent can find a failing rollout, and an operator agent can immediately use `fail_deployment` to stop it. This allows for coordinated, multi-agent incident response.

This server supports stdio, SSE, and Streamable HTTP transports. When running CrewAI locally, stdio works best for quick scripts. For production deployments in cloud environments, use the SSE or Streamable HTTP endpoint provided by Vinkius.

Your agents call `get_job` to retrieve the raw configuration for any active workload. Your research agent can read this file to understand the environment variables and volume mounts. It helps your crew suggest configuration fixes when tasks fail to start.

Yes, because the MCP Server only accesses job configurations, node statuses, and allocation logs, never raw host files. Vinkius hosts the connection in an isolated sandbox, ensuring your authentication tokens remain hidden. Your Python agents only interact with the structured JSON output of the tools.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript