3,400+ MCP servers ready to use
Vinkius

StayFi MCP Server for CrewAIGive CrewAI instant access to 17 tools to Check Stayfi Status, Export Guests, Get Analytics, and more

Built by Vinkius GDPR 17 Tools Framework

Connect your CrewAI agents to StayFi through Vinkius, pass the Edge URL in the `mcps` parameter and every StayFi tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this App Connector for CrewAI

The StayFi app connector for CrewAI is a standout in the Marketing Automation category — giving your AI agent 17 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="StayFi Specialist",
    goal="Help users interact with StayFi effectively",
    backstory=(
        "You are an expert at leveraging StayFi 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 StayFi "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 17 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
StayFi
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 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.

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.

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

Who is it for?

Tailor-made for vacation rental managers, boutique hoteliers, and hospitality operators looking to maximize direct bookings through captive portal data collection.

The StayFi MCP Server exposes 17 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.

All 17 StayFi tools available for CrewAI

When CrewAI connects to StayFi through Vinkius, your AI agent gets direct access to every tool listed below — spanning wifi-marketing, guest-capture, email-marketing, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

check_stayfi_status

Verify connectivity

export_guests

Export guest data

get_analytics

Get analytics overview

get_device_status

Get device status

get_email_stats

Get email collection stats

get_guest

Get guest details

get_network

Get network details

get_property

Get property details

get_property_stats

Get property stats

get_splash_page

Get splash page

list_devices

List hardware devices

list_guests

List all guests

list_guests_by_property

List guests by property

list_networks

List WiFi networks

list_properties

List properties

list_splash_pages

List splash pages

search_guests

Search guests

Connect StayFi to CrewAI via MCP

Follow these steps to wire StayFi into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 17 tools from StayFi

Why Use CrewAI with the StayFi MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with StayFi through the Model Context Protocol.

01

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

02

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

03

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

04

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 + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries StayFi for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries StayFi, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain StayFi tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries StayFi against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for StayFi in CrewAI

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

01

"Show all guests captured via WiFi at our beach property this week."

02

"Are all StayFi routers online and functioning correctly?"

03

"What is our email collection rate across all properties for the current month?"

Troubleshooting StayFi MCP Server with CrewAI

Common issues when connecting StayFi to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

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.

StayFi + CrewAI FAQ

Common questions about integrating StayFi MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.