Does Vinsight work for breweries too?

Yes! Vinsight manages wine, beer, and spirits production. The same API covers all beverage types — wineries, breweries, and distilleries.

Vinsight MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Vinsight
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Vinsight through Vinkius, pass the Edge URL in the `mcps` parameter and every Vinsight 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="Vinsight Specialist",
    goal="Help users interact with Vinsight effectively",
    backstory=(
        "You are an expert at leveraging Vinsight 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 Vinsight "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 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 Vinsight MCP Server

Connect your Vinsight operation to any AI agent and manage your entire beverage production business through natural conversation.

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

Stock Items — Search your product catalog: wines, beers, spirits, and raw materials with pricing and compliance codes
Sales Orders — Track orders: customer, items, totals, status, and shipping across all channels
Production Orders — Monitor production runs: input materials, output products, vessel assignments
Batches — Track individual lots through the production lifecycle with batch codes and vintage
Vessels — Monitor tanks, fermenters, barrels, and bright tanks with capacity and fill levels
Lab Results — View QC analyses: pH, TA, alcohol, SO₂, dissolved oxygen, and residual sugar
Inventory — Real-time stock levels across all warehouses: available, committed, and on-order
Contacts — Manage customers, suppliers, and distributors
Purchase Orders — Track incoming materials: grapes, bottles, corks, chemicals

The Vinsight MCP Server exposes 12 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 Vinsight to CrewAI via MCP

Follow these steps to integrate the Vinsight 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 12 tools from Vinsight

Why Use CrewAI with the Vinsight MCP Server

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

Vinsight + CrewAI Use Cases

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

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

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

Vinsight MCP Tools for CrewAI (12)

These 12 tools become available when you connect Vinsight to CrewAI via MCP:

get_sales_order

Get order details

get_stock_item

The definitive product record. Get product details

list_batches

Track individual lots through the production lifecycle. List production batches

list_lab_results

Sorted by date. For quality control and compliance monitoring. List lab analysis results

list_production_orders

Tracks the winemaking or brewing process. List production orders

list_purchase_orders

Supply chain tracking for production inputs. List purchase orders

list_sales_orders

Core revenue tracking for wineries and breweries. List sales orders

list_stock_levels

Critical for fulfillment and reorder decisions. List current inventory

list_vessels

With capacity, current contents, fill level, and location. For cellar space planning. List tanks and barrels

list_warehouses

For multi-site inventory management. List warehouses

search_contacts

Returns contact profile, type, addresses, payment terms, and order history. Search contacts

search_stock_items

Returns product details including SKU, description, unit of measure, price, tax code, and current stock level. Works for wine, beer, spirits, and raw materials. Search wine/beer/spirit products

Example Prompts for Vinsight in CrewAI

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

"What's our current Chardonnay 2024 inventory?"

"Create a new production order to blend 500L of 'Batch 44' into Tank 12."

"Check the latest lab results for the Pinot Noir fermentations in Tank B."

Troubleshooting Vinsight MCP Server with CrewAI

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

Vinsight + CrewAI FAQ

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