How is eCellar different from Commerce7?

eCellar is an all-in-one DTC platform popular with ultra-premium Napa Valley and Sonoma wineries. It includes CRM, ecommerce, POS, wine clubs, and reservations in a unified system with full REST API.

Does this integration require additional licensing from eCellar?

No, the Exchange REST API is generally available to all eCellar customers. You simply need to request your unique API Key and Secret from the eCellar support team as mentioned in the instructions.

Can I manage reservations with this tool?

Yes! The integration provides full access to your reservation and booking systems, allowing you to quickly query upcoming visits, manage guest lists, and track tasting room capacity.

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

Name: eCellar
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your eCellar winery to any AI agent and manage your premium DTC operation through natural conversation.

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

Customers — Search by name, email, or phone; view lifetime spend, club status, and tasting room history
Orders — Track online, tasting room, phone, and club shipment orders with full line items
Wine Clubs — Manage membership tiers, allocation, and shipment schedules
Products — Browse your wine catalog with pricing, tasting notes, and stock levels
Reservations — View and manage tasting room bookings by date
Inventory — Real-time stock across all locations: available, allocated, and on-hand

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

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

Why Use CrewAI with the eCellar MCP Server

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

eCellar + CrewAI Use Cases

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

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

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

eCellar MCP Tools for CrewAI (10)

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

get_customer

For VIP identification and personalized service. Get customer profile

get_order

Get order details

get_product

Get wine details

list_club_members

For retention and engagement tracking. List club members

list_clubs

Essential for DTC revenue planning. List wine clubs

list_inventory

Multi-location inventory management. List wine inventory

list_orders

With line items, totals, payment, and fulfillment status. List wine orders

list_products

The product catalog powering ecommerce and POS. List wine catalog

list_reservations

Filter by date for daily planning. List tasting reservations

search_customers

Returns profile, lifetime spend, wine club membership, tasting room visits, and purchase history. Core CRM data for personalized wine recommendations. Search wine customers

Example Prompts for eCellar in CrewAI

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

"Who are our top 5 customers by lifetime spend?"

"Search for inventory levels of the 2019 Reserve Cabernet."

"Show me the reservation schedule for tomorrow afternoon."

Troubleshooting eCellar MCP Server with CrewAI

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

eCellar + CrewAI FAQ

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