How do I get an EZO API Key?

Log in to your EZO.io account, navigate to **Settings > API Integration**, and you can enable the API and retrieve your unique **Secret API Key**. You also need your **Subdomain** (the prefix in your account URL).

Does the integration support multiple locations?

Yes, you can use the list_asset_locations tool to see all physical sites and sub-locations configured in your EZO account, and filter assets by location.

Can the agent perform asset checkouts?

This integration currently focuses on listing and auditing assets, inventory, and members. Performing live checkouts or scanning barcodes should be managed via the EZO.io mobile app or web interface.

EZO Asset Intelligence MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: EZO Asset Intelligence
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to EZO Asset Intelligence through the Vinkius — pass the Edge URL in the `mcps` parameter and every EZO Asset Intelligence tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="EZO Asset Intelligence Specialist",
    goal="Help users interact with EZO Asset Intelligence effectively",
    backstory=(
        "You are an expert at leveraging EZO Asset Intelligence tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in EZO Asset Intelligence "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

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 EZO Asset Intelligence MCP Server

Integrate EZO.io (formerly EZOfficeInventory), the world's most popular asset management platform, directly into your AI workflow. Manage your fixed asset database and physical locations, track consumable inventory and real-time stock levels, monitor active checkouts and reservations, and oversee your entire asset lifecycle using natural language.

When paired with CrewAI, EZO Asset Intelligence becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call EZO Asset Intelligence tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Asset Oversight — List and retrieve detailed information, identifiers, and maintenance history for all your managed assets.
Inventory Intelligence — Monitor consumable inventory items, resolving available quantities and stock thresholds across your organization.
Checkout Management — Access and monitor currently checked out assets, identifying assigned members and expected return dates.
Asset Auditing — Retrieve high-level summaries of asset volume, location distribution, and organizational resource health instantly.

The EZO Asset Intelligence MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI 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 EZO Asset Intelligence to CrewAI via MCP

Follow these steps to integrate the EZO Asset Intelligence MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from EZO Asset Intelligence

Why Use CrewAI with the EZO Asset Intelligence MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with EZO Asset Intelligence through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

EZO Asset Intelligence + CrewAI Use Cases

Practical scenarios where CrewAI combined with the EZO Asset Intelligence MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries EZO Asset Intelligence for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries EZO Asset Intelligence, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain EZO Asset Intelligence tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries EZO Asset Intelligence against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

EZO Asset Intelligence MCP Tools for CrewAI (10)

These 10 tools become available when you connect EZO Asset Intelligence to CrewAI via MCP:

get_asset_detailed_data

Get detailed settings and information for a specific asset

get_ezo_account_metadata

Retrieve metadata and limits for your EZO account

list_account_members

List all members and users registered in your organization

list_asset_locations

List all physical locations and sub-locations configured in your account

list_available_assets

Identify assets that are currently available for checkout

list_consumable_inventory

List all consumable inventory items and their stock levels

list_currently_checked_out_assets

Identify all assets that are currently checked out to members

list_managed_assets

g. available, checked out) from the EZO API. List all fixed assets managed in your EZO account

list_overdue_checkouts

Identify assets that are past their expected return date (mock logic)

quick_asset_volume_audit

Retrieve a high-level summary of assets, inventory, and members

Example Prompts for EZO Asset Intelligence in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with EZO Asset Intelligence immediately.

"List all assets currently checked out."

"Show me our inventory levels for 'Ethernet Cables'."

"Check for overdue asset returns."

Troubleshooting EZO Asset Intelligence MCP Server with CrewAI

Common issues when connecting EZO Asset Intelligence to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

EZO Asset Intelligence + CrewAI FAQ

Common questions about integrating EZO Asset Intelligence MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.