Bring Lawn Care
to CrewAI
Learn how to connect TurfHop 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.
What is the TurfHop MCP Server?
Connect your TurfHop account to any AI agent and simplify how you coordinate your field service operations, scheduling, and billing through natural conversation.
What you can do
- Customer Management — List and search customer records, create new profiles, and retrieve complete service histories.
- Job Scheduling — List all service jobs, create new assignments, and update job details or statuses programmatically.
- Billing & Invoicing — Monitor your cash flow by listing invoices, quotes, and payment statuses for your services.
- Service Catalog — Browse your offered products and services to identify pricing and availability.
- Operational tracking — Fetch detailed metadata for specific jobs or customers to stay on top of your mobile workforce.
How it works
1. Subscribe to this server
2. Enter your TurfHop API Key (found in your account settings)
3. Start managing your field services from Claude, Cursor, or any MCP client
Who is this for?
- Field Service Business Owners — quickly check job statuses and manage client records via simple AI commands.
- Operations Managers — schedule new assignments and track team progress directly from the workspace.
- Administrative Staff — monitor invoices and quotes to maintain an organized billing cycle via the AI assistant.
Built-in capabilities (12)
Pass customer data as a JSON string. Create a new customer
Pass job data as a JSON string. Create a new service job
Get customer details by ID
Get invoice details
Get job details
List all customers
List all invoices
List all service jobs
List all products and services
List all quotes
Update an existing customer
Update an existing job
Why CrewAI?
When paired with CrewAI, TurfHop becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TurfHop 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
TurfHop in CrewAI
TurfHop and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TurfHop 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 TurfHop in CrewAI
The TurfHop 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
TurfHop for CrewAI
Every tool call from CrewAI to the TurfHop MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for a customer by their name?
Yes! Use the list_customers tool. While it returns the full list, you can ask the AI agent to find a specific person or retrieve details for a specific ID using get_customer.
How do I schedule a new service job via AI?
Use the create_job action. You'll need to provide a JSON string containing the job details like customer_id, title, and start_date to register the new assignment.
Is it possible to see the payment status of an invoice?
Absolutely. Use the get_invoice tool and provide the Invoice ID. The agent will retrieve the complete metadata, including whether the invoice is paid, pending, or overdue.
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.