How do I get InnoVint API access?

Contact InnoVint support at support@innovint.us to request a Personal Access Token. You'll need an active InnoVint account.

Can I record lab analysis results using this integration?

Yes, you can input new lab readings such as pH, TA, Brix, and free SO2 directly for a specific lot or vessel using natural language, and the AI will post them to the InnoVint API.

Does this support managing multiple wineries under the same account?

Yes, if your InnoVint integrator account has access to multiple wineries, you can scope your API requests to a specific Winery ID to manage lots and vessels across different properties.

InnoVint MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: InnoVint
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your InnoVint winery to any AI agent and transform how your cellar team works — from harvest intake to bottling.

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

What you can do

Lots — Search and track wine lots by varietal, vintage, lot code, or vessel assignment
Vessels — Monitor tanks, barrels, concrete eggs, and amphorae — capacity, fill level, and contents
Lab Analyses — View pH, TA, SO2, Brix, RS, VA, and alcohol readings for any lot over time
Cellar Actions — Track rackings, pump-overs, punchdowns, additions, fining, and filtration history
Wines & Vintages — Browse wine products and navigate production by vintage year
Additives — Reference registered chemicals, enzymes, and fining agents with dosage guidelines
Multi-Winery — Manage multiple wineries from a single AI connection

The InnoVint 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 InnoVint to CrewAI via MCP

Follow these steps to integrate the InnoVint 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 InnoVint

Why Use CrewAI with the InnoVint MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with InnoVint 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 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

InnoVint + CrewAI Use Cases

Practical scenarios where CrewAI combined with the InnoVint MCP Server delivers measurable value.

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

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

InnoVint MCP Tools for CrewAI (10)

These 10 tools become available when you connect InnoVint to CrewAI via MCP:

get_lot

The primary data point for any winemaking question. Get full lot details

get_vessel

Essential for barrel program management. Get vessel details

list_actions

Filter by lot to see complete cellar history. List cellar actions

list_additives

With regulatory limits and typical dosage. List additives

list_analyses

Filter by lot to see a specific wine's chemistry over time. List lab analyses

list_vessels

Shows capacity, current contents, fill level, and location. Critical for cellar management and space planning. List tanks and barrels

list_vintages

Navigate wine production by year. List vintages

list_wineries

Multi-winery operations can manage several facilities from one account. List wineries

list_wines

Each with varietal rules, appellation, and production notes. List wine products

search_lots

Returns lot details including volume, vessel assignment, varietal composition, and current status. Essential for tracking individual batches through the winemaking process — from harvest intake to bottling. Search wine lots

Example Prompts for InnoVint in CrewAI

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

"How is the 2025 Pinot Noir fermentation going?"

"Record a new lab reading for the 2025 Chardonnay: pH is 3.32 and TA is 6.5 g/L."

"Which vessels are currently empty and available for the upcoming harvest?"

Troubleshooting InnoVint MCP Server with CrewAI

Common issues when connecting InnoVint 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

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

InnoVint + CrewAI FAQ

Common questions about integrating InnoVint 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.