Bring Lawn Care
to Cursor
Learn how to connect TurfHop to Cursor 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 Cursor?
Cursor's Agent mode turns TurfHop into an in-editor superpower. Ask Cursor to generate code using live data from TurfHop and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
TurfHop in Cursor
TurfHop and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TurfHop to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.