Bring Property Management
to CrewAI
Learn how to connect Mews to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Mews MCP Server?
Connect your Mews hotel to any AI agent and transform your front desk into an intelligent, voice-ready concierge.
What you can do
- Reservations — Today's check-ins, upcoming arrivals, room assignments, and booking status
- Guests — Search profiles, loyalty tiers, preferences, allergies, and past stays
- Rooms — Real-time room status: vacant/occupied, housekeeping (clean/dirty/inspected)
- Billing — Guest folios, charges, payments, and balance tracking
- Rates & Services — Rate plans, bookable services, and POS outlet items
- Property — Hotel configuration, departments, and operational settings
Who is this for?
- Front Desk — "Who is checking in today? Any VIP arrivals?" — instant morning briefing
- Revenue Managers — Rate plan performance, occupancy trends, and ADR analysis
- Housekeeping — Room status dashboard, turnover priorities, and out-of-order tracking
- General Managers — Daily operational KPIs across all departments
Built-in capabilities (12)
Get guest profile
Get hotel configuration
Get reservation details
Filter by date range. THE core tool — "Who is checking in today?" "How many rooms tonight?" Get hotel reservations
Filter by guest for their complete financial history. List guest bills
With pricing and categories. List POS items
With amounts, dates, and settlement status. List payments
With pricing, restrictions, and availability rules. List room rates
With dates, room types, and release dates. List room blocks
List hotel rooms
List hotel services
Returns profile, contact info, nationality, loyalty status, past stays, preferences, and billing history. Search hotel guests
Why CrewAI?
When paired with CrewAI, Mews becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Mews 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
Mews in CrewAI
Mews and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mews 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 | 3,400+ 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 Mews in CrewAI
The Mews 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 12 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
Mews for CrewAI
Every tool call from CrewAI to the Mews MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What types of hotels use Mews?
Mews serves 5,000+ properties in 85+ countries — from boutique hotels and hostels to luxury resorts and hotel groups. It's a cloud-native PMS designed for modern hospitality.
Is the Mews API suitable for large hotel groups?
Yes, Mews provides a robust API that supports multi-property operations, making it ideal for hotel groups to manage central reservations, corporate billing, and group-wide reporting.
Can I check room housekeeping status in real-time?
Yes, you can query Mews to get the real-time status of any room, including whether it is clean, dirty, inspected, or out of order, which helps prioritize housekeeping efforts.
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.