How do I get an Envi API Key?

Log in to your Envi administrator portal, navigate to **Settings > API Integration**, and you can generate or retrieve your unique **REST API Key** from there. Ensure your user has the 'API Access' permission enabled.

Does the integration support multiple facilities?

Yes, you can use the list_medical_inventory_levels and list_healthcare_facilities tools to retrieve data across all hospitals, clinics, and warehouses in your network.

Can the agent place new supply orders?

This integration currently focuses on listing and auditing purchase orders, inventory, and requisitions. Creating new POs or requisitions should be managed via the Envi web application to ensure proper clinical approvals.

Envi Healthcare Supply Chain MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Envi Healthcare Supply Chain
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Envi Healthcare Supply Chain through the Vinkius — pass the Edge URL in the `mcps` parameter and every Envi Healthcare Supply Chain 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="Envi Healthcare Supply Chain Specialist",
    goal="Help users interact with Envi Healthcare Supply Chain effectively",
    backstory=(
        "You are an expert at leveraging Envi Healthcare Supply Chain 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 Envi Healthcare Supply Chain "
        "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 Envi Healthcare Supply Chain MCP Server

Integrate Envi, the leading supply chain and inventory management platform for healthcare, directly into your AI workflow. Manage your healthcare purchase orders across facilities, track real-time medical supply inventory and stock levels, monitor authorized vendors and suppliers, and oversee your clinical procurement using natural language.

When paired with CrewAI, Envi Healthcare Supply Chain becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Envi Healthcare Supply Chain 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

PO Oversight — List and retrieve detailed information, line items, and approval status for all your healthcare purchase orders.
Inventory Intelligence — Monitor real-time medical supply stock across facilities and departments, resolving clinical SKUs and quantities.
Vendor Management — Access and monitor authorized medical vendors and suppliers, identifying contract details and sourcing origins.
Supply Auditing — Retrieve high-level summaries of PO volume, critical stock alerts, and organizational facility health instantly.

The Envi Healthcare Supply Chain 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 Envi Healthcare Supply Chain to CrewAI via MCP

Follow these steps to integrate the Envi Healthcare Supply Chain 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 Envi Healthcare Supply Chain

Why Use CrewAI with the Envi Healthcare Supply Chain MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Envi Healthcare Supply Chain 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

Envi Healthcare Supply Chain + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Envi Healthcare Supply Chain MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Envi Healthcare Supply Chain 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 Envi Healthcare Supply Chain, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Envi Healthcare Supply Chain 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 Envi Healthcare Supply Chain against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Envi Healthcare Supply Chain MCP Tools for CrewAI (10)

These 10 tools become available when you connect Envi Healthcare Supply Chain to CrewAI via MCP:

get_envi_account_metadata

Retrieve metadata and limits for your Envi account

get_po_technical_details

Get detailed settings and line items for a specific purchase order

get_supply_stock_level

Get real-time stock levels for a specific medical item

list_critical_stock_alerts

Identify medical supplies that are currently below safety thresholds (mock logic)

list_healthcare_facilities

List all facilities and clinics configured in your organization

list_healthcare_pos

List all purchase orders in your Envi account

list_latest_supply_requisitions

Identify the most recently created or updated supply requisitions

list_medical_inventory_levels

List inventory levels across all facilities and locations

list_medical_vendors

List all authorized vendors and suppliers in your network

quick_healthcare_supply_audit

Retrieve a high-level summary of POs, inventory, and requisitions

Example Prompts for Envi Healthcare Supply Chain in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Envi Healthcare Supply Chain immediately.

"List all pending healthcare purchase orders."

"What is the stock level for 'Sterile Gauze' at Main Hospital?"

"Show me our authorized medical vendors."

Troubleshooting Envi Healthcare Supply Chain MCP Server with CrewAI

Common issues when connecting Envi Healthcare Supply Chain 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.

Envi Healthcare Supply Chain + CrewAI FAQ

Common questions about integrating Envi Healthcare Supply Chain 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.