How to Use the EZO Asset Intelligence MCP in CrewAI

Q: How do I pass the EZO Asset Intelligence MCP server to a CrewAI agent?

Install the library using pip install crewai "crewaitools". You can then pass your Vinkius server URL directly into the agent's mcps list to give them instant access to the EZO tools.

Q: Can I limit which tools a CrewAI agent can use from EZO Asset Intelligence?

Yes. You can use the MCPServerHTTP class from crewai.mcp and apply a toolfilter to only expose read tools like listavailableassets while hiding administrative tools.

Q: How do CrewAI agents share EZO Asset Intelligence data between themselves?

CrewAI agents use shared memory. When one agent runs getassetdetaileddata to inspect a laptop, the resulting JSON is stored and made available to the next agent in the execution sequence.

Coordinate teams of specialized agents to manage your physical hardware using CrewAI and EZO Asset Intelligence.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect EZO Asset Intelligence MCP to CrewAI

Create your Vinkius account to connect EZO Asset Intelligence 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 EZO Asset Intelligence with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate EZO audits with a CrewAI agent team

This setup uses `quick_asset_volume_audit` and `list_managed_assets` to let a specialized CrewAI auditing crew reconcile your physical and digital records. One CrewAI agent pulls the raw EZO inventory counts while a second agent analyzes the data for discrepancies. By splitting the work, you prevent a single CrewAI agent from getting bogged down in large EZO asset lists. The agents pass the filtered EZO data back and forth using CrewAI's shared memory.

Let a CrewAI team manage overdue physical assets

The server exposes `list_overdue_checkouts` and `list_currently_checked_out_assets` to let a multi-agent CrewAI team track down missing company equipment. A CrewAI tracker agent monitors the return dates while a communications agent drafts follow-up emails to the users. This autonomous CrewAI setup runs entirely in the background without human intervention. You define the escalation path, and the CrewAI agents execute the EZO tools sequentially to keep your inventory accurate.

Deploy this MCP Server for multi-site asset tracking

This server provides `list_asset_locations` and `list_available_assets` to let your CrewAI agents coordinate physical equipment distribution across multiple offices. A CrewAI logistics agent checks which sites have surplus laptops and which are running low on gear. The CrewAI crew uses this physical EZO location data to suggest transfers before you waste budget buying new hardware. It is EZO operations tracking handled entirely by specialized, collaborating CrewAI agents.

Setup guide

Set up EZO Asset Intelligence 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 EZO Asset Intelligence tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

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

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

Install the library using `pip install crewai "crewai[tools]"`. You can then pass your Vinkius server URL directly into the agent's `mcps` list to give them instant access to the EZO tools.

Yes. You can use the `MCPServerHTTP` class from `crewai.mcp` and apply a `tool_filter` to only expose read tools like `list_available_assets` while hiding administrative tools.

CrewAI agents use shared memory. When one agent runs `get_asset_detailed_data` to inspect a laptop, the resulting JSON is stored and made available to the next agent in the execution sequence.

Yes. CrewAI is compatible with stdio, SSE, and Streamable HTTP transports, allowing you to connect to your managed Vinkius MCP Server using whatever connection method fits your deployment.

Vinkius hosts the server in a zero-trust, ephemeral V8 sandbox. Your EZO API tokens and physical asset records are never exposed to the LLM or stored in the agent's memory logs.

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