Is Wine-Searcher API free?

Wine-Searcher offers a free trial (100 calls/day). After the trial, paid plans are available based on daily call volume.

Wine-Searcher MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: Wine-Searcher
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

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

Connect to Wine-Searcher — the world's largest wine price comparison engine — and access real-time market intelligence for any wine.

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

Wine Check — Look up any wine: critic scores, grape varieties, region, alcohol content, and global average/min/max pricing
Market Price — Compare real-time pricing from 100,000+ merchants: shop names, locations, and direct purchase URLs
Search Wines — Full-text search across the entire Wine-Searcher database for discovery and exploration
Grape Info — Detailed grape variety profiles: origins, growing regions, wine styles, and food pairings
Region Info — Wine region deep-dives: climate, soil, appellations, and notable producers
Producer Info — Winery profiles: key wines, price ranges, scores, and available vintages

The Wine-Searcher MCP Server exposes 6 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 Wine-Searcher to CrewAI via MCP

Follow these steps to integrate the Wine-Searcher 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 6 tools from Wine-Searcher

Why Use CrewAI with the Wine-Searcher MCP Server

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

Wine-Searcher + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Wine-Searcher MCP Server delivers measurable value.

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

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

Wine-Searcher MCP Tools for CrewAI (6)

These 6 tools become available when you connect Wine-Searcher to CrewAI via MCP:

grape_info

Perfect for sommelier education and pairing recommendations. Get grape variety info

market_price

Use for price comparison, market analysis, or finding the best deal on a specific wine. Get global market pricing

producer_info

Use for winery research and brand comparison. Get producer/winery info

region_info

Essential for terroir education and regional exploration. Get wine region info

search_wines

Returns matching wines with pricing, scores, and merchant availability. Use for discovery and exploration. Search the wine database

wine_check

), grape varieties, region, appellation, alcohol content, average/min/max pricing across global merchants. The primary lookup tool for any wine question. Check wine details and scores

Example Prompts for Wine-Searcher in CrewAI

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

"What's the average price for Opus One 2021?"

"Find merchants near London selling Dom Pérignon 2012."

"What can you tell me about the Pomerol wine region?"

Troubleshooting Wine-Searcher MCP Server with CrewAI

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

Wine-Searcher + CrewAI FAQ

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