Bring Wifi Marketing
to CrewAI
Learn how to connect StayFi to CrewAI and start using 17 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the StayFi MCP Server?
Transform your vacation rental network into a powerful marketing engine by connecting your AI agents to StayFi. With 17 dedicated tools, your AI can automatically pull guest contact data, monitor router health, configure splash pages, and analyze email collection rates across your portfolio.
What you can do
- Capture and export guest emails and phone numbers
- Manage vacation rental properties and networks
- Configure custom WiFi splash and login pages
- Monitor router health and online status in real-time
- Track email collection and marketing analytics
- Organize and segment guest lists for CRM integration
How it works
1. Subscribe to this server 2. Enter your StayFi API Key (found in your provider dashboard) 3. Let your AI agents seamlessly manage your WiFi marketing via VinkiusWho is it for?
Tailor-made for vacation rental managers, boutique hoteliers, and hospitality operators looking to maximize direct bookings through captive portal data collection.Built-in capabilities (17)
Verify connectivity
Export guest data
Get analytics overview
Get device status
Get email collection stats
Get guest details
Get network details
Get property details
Get property stats
Get splash page
List hardware devices
List all guests
List guests by property
List WiFi networks
List properties
List splash pages
Search guests
Why CrewAI?
When paired with CrewAI, StayFi becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call StayFi 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
StayFi in CrewAI
StayFi and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect StayFi 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 StayFi in CrewAI
The StayFi 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 17 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
StayFi for CrewAI
Every tool call from CrewAI to the StayFi MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can my AI retrieve the list of guests who connected to the WiFi at a specific property?
Simply use the get_property_guests tool providing the specific property ID. Your agent will instantly compile a list of all guests captured via the captive portal, including their names, emails, and phone numbers.
Can I automatically check if all my routers are online across my portfolio?
Yes! Ask the agent to run the check_router_health action. It will scan all your StayFi routers in real-time and report back any offline devices, ensuring your guest networks are always functional.
Is it possible to track the total number of emails collected this month?
Absolutely. By utilizing the get_collection_stats tool, your agent can instantly fetch the email collection analytics across all properties, giving you an immediate view of your marketing data growth.
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.