How to Use the Fusion Operations MCP in CrewAI

Q: How do I hook up Fusion Operations to CrewAI?

Install crewaitools. You can pass the endpoint directly in your agent configuration using the mcp array. The crew will automatically discover the manufacturing tools.

Q: Can I restrict which Fusion Operations tools my CrewAI agents see?

You control exactly what they access. Use MCPServerHTTP from the framework and apply a tool filter. You probably don't want your research agent having access to the order creation endpoint.

Build autonomous factory management teams using CrewAI and this industrial control backend.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Fusion Operations MCP to CrewAI

Create your Vinkius account to connect Fusion Operations 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 Fusion Operations with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Inventory Control

Stop managing supply chains manually. You can spin up a CrewAI monitor agent that constantly watches `list_inventory_stocks`. When bearings drop below fifty units, it flags the issue to an action agent. That second agent immediately executes `create_production_order` to replenish the bins. They share memory, so the action agent knows exactly why the monitor triggered the alarm. You just watch the logs.

Autonomous Shift Coordination

Your floor supervisors spend half their day matching people to equipment. Hand that off to a specialized scheduling crew. One agent maps out the hardware using `list_floor_machines`. A second agent cross-references that map against `list_floor_workers`. If a milling machine needs an operator, the crew finds the right person and assigns them. The MCP standard makes these API calls dead simple for the agents to execute.

Quality Control Crews via MCP

Finding bottlenecks requires digging through massive amounts of historical data. Assign a research agent to pull `list_production_records` and analyze completion times across shifts. It can drill down into specific steps using `list_manufacturing_operations`. When the agent finds a slow step, it escalates a report to your human managers. The crew works in the background while your factory runs.

Setup guide

Set up Fusion Operations 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 Fusion Operations tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Fusion Operations 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="Fusion Operations Analyst",
        goal="Access and analyze Fusion Operations data via MCP.",
        backstory="Expert analyst with direct Fusion Operations access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Fusion Operations 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 Fusion Operations. 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 Fusion Operations 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 Fusion Operations MCP in CrewAI

Install `crewai[tools]`. You can pass the endpoint directly in your agent configuration using the mcp array. The crew will automatically discover the manufacturing tools.

You control exactly what they access. Use `MCPServerHTTP` from the framework and apply a tool filter. You probably don't want your research agent having access to the order creation endpoint.

CrewAI handles shared memory natively. If Agent A pulls inventory stocks from the MCP Server, Agent B knows the exact counts without having to hit the endpoint a second time.

The action agent receives the error from the tool call. Depending on your instructions, it can either retry the command or escalate the failure to a moderator agent.

We route everything through a heavily sandboxed API layer. Your agents can read proprietary product specifications and manufacturing steps, but the connection requires a single endpoint token and drops immediately after use.

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