Compatible with every major AI agent and IDE
What is the CellarPass MCP Server?
Connect your CellarPass tasting room to any AI agent and transform how you manage guest experiences.
What you can do
- Reservations — View today's bookings, upcoming reservations, and guest details by date
- Experiences — Browse all tasting experiences: Reserve Tasting, Vineyard Tour, Food & Wine Pairing, Private Cellar
- Availability — Check open time slots for any experience on any date
- Venues — Manage multiple tasting room locations with hours and capacity
- Guests — Search guest profiles: visit history, favorite experiences, spending, and VIP status
Who is this for?
- Tasting Room Managers — "Who's coming today? Any VIPs?" — instant daily briefing
- Hospitality Directors — Guest recognition, experience optimization, and capacity planning
- Winery Owners — Revenue per guest, popular experiences, and seasonal trends
- Events Coordinators — Booking management for private events and corporate tastings
Built-in capabilities (8)
Essential for booking coordination. Check booking availability
Get experience details
For pre-visit preparation. Get reservation details
Get venue details
With pricing, duration, capacity, and description. List tasting experiences
Filter by date for daily planning. THE core tool for tasting room managers — "Who's coming today?" List tasting reservations
For multi-location wineries. List tasting venues
Returns visit history, favorite experiences, spending, and VIP status. For personalized hospitality. Search guests
Why CrewAI?
When paired with CrewAI, CellarPass becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CellarPass tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
CellarPass in CrewAI
CellarPass and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect CellarPass to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for CellarPass in CrewAI
The CellarPass 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. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
CellarPass for CrewAI
Every tool call from CrewAI to the CellarPass MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How many wineries use CellarPass?
CellarPass serves 800+ wineries across Napa Valley, Sonoma, Oregon, Washington, and other premier wine regions. It's the #1 tasting room reservation platform.
Can I flag or review VIP guest history using this integration?
Yes! Your AI can pull visitor profiles and tag high-revenue VIPs, highlighting lifetime spend seamlessly when generating your daily prep reviews.
Does it manage multiple tasting room venues?
Correct. With 'Venues' configuration endpoints natively wired, the AI can cross-reference capacities against your separate tasting properties in a single conversational flow.
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.
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.
Explore More MCP Servers
View all →
Unpaywall (Open Access Papers)
1 toolsAccess millions of open-access scholarly articles. Check OA status and retrieve full-text PDF links using DOIs.

Square
10 toolsManage payments, orders, catalog, customers, inventory, locations, and team members for your Square business through natural conversation.

CloudConvert
11 toolsConvert files between 200+ formats including PDF, images, video, and documents with a fast cloud-based processing engine.

OFX Bank Statement Parser
1 toolsTurn archaic OFX/QFX bank exports into clean JSON transactions safely and local. Let your AI act as your personal accountant without uploading sensitive financial data.
