Can my AI automatically pull tasting notes and pairings out of a single bottle search?

Yes! Use the `get_wine_detail` and `get_pairings` tools. Your agent will respond with complete metadata regarding aromas, tannin complexity, and best foods to match with the queried bottle.

How do I easily update the inventory inside my virtual cellar?

Simply ask the agent to run the `add_wine_to_cellar` action providing the Wine ID and Quantity. It will modify your inventory database safely without manually clicking through menus.

Are there any destructive capabilities regarding regional scores or public metrics?

No. The core set of tools dealing with global data limits itself strictly to querying records like `get_vintage_scores`. All write operations are firmly locked to your private user cellar.

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

Name: Winevybe
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your Winevybe developer account to any AI agent and take full control of sommelier intelligence and wine inventory tracking through natural conversation.

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

Sommelier Recommender — Query for specific wine pairings and tasting notes magically linked behind intelligent algorithms
Inventory Management — Read and append bottle quantities to persistent user cellars safely via automated workflows
Vintage Auditing — Cross-reference a specific year to see if the region's climate conditions yielded good harvests
Pricing Comparisons — Compare distinct bottles instantly to analyze pricing versus critical community reception
Vineyard Profiling — Retrieve the underlying history and details of major worldwide producers and regions

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

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

Why Use CrewAI with the Winevybe MCP Server

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

Winevybe + CrewAI Use Cases

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

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

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

Winevybe MCP Tools for CrewAI (10)

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

add_wine_to_cellar

Add a purchased bottle into a users virtual cellar tracker

compare_wines

Generate a side-by-side contrast of two bottles

get_pairings

Get food pairing recommendations for a specific wine

get_region_info

Retrieve details about wine-making appellations

get_reviews

Get community tasting reviews and ratings

get_user_cellar

Examine the inventory of an authenticated users wine cellar

get_vintage_scores

Get an overview of harvest qualities by year

get_wine_detail

Get profound tasting notes and stats on a specific wine

get_winery_info

Get profiles of specific vineyards and producers

search_wines

Search the Winevybe database for specific bottles

Example Prompts for Winevybe in CrewAI

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

"Search for details on the Screaming Eagle Cabernet Sauvignon."

"Compare wine 4902 and wine 5910."

"Check my virtual cellar inventory."

Troubleshooting Winevybe MCP Server with CrewAI

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

Winevybe + CrewAI FAQ

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