2,500+ MCP servers ready to use
Vinkius

WorkWave MCP Server for Cursor 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install WorkWave and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "workwave": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
WorkWave
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 WorkWave MCP Server

Connect your WorkWave Service account to any AI agent and manage your field service operations through natural conversation.

Cursor's Agent mode turns WorkWave into an in-editor superpower. Ask Cursor to generate code using live data from WorkWave and it fetches, processes, and writes — all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Service Orders — Browse and list all work requests, retrieve full details for specific orders, and update lifecycle statuses (e.g., InProgress, Completed)
  • Customer Accounts — List all field service accounts and retrieve comprehensive details including contact info, billing history, and service locations
  • Field Personnel — List all registered technicians and field staff, and retrieve profile details to check roles, skills, and contact info
  • Equipment Inventory — Monitor and audit managed assets and equipment used across your field service operations directly from your agent
  • Site Discovery — Retrieve physical service locations and job site addresses, including geographical coordinates for routing purposes
  • Operational Insights — Quickly find unique account, order, employee, and location IDs required for automated field service workflows
  • Health Monitoring — Verify the connectivity and status of your WorkWave API integration to ensure real-time data sync

The WorkWave MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect WorkWave to Cursor via MCP

Follow these steps to integrate the WorkWave MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using WorkWave

Open Agent mode in chat and ask: "Using WorkWave, help me..."10 tools available

Why Use Cursor with the WorkWave MCP Server

Cursor AI Code Editor provides unique advantages when paired with WorkWave through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

WorkWave + Cursor Use Cases

Practical scenarios where Cursor combined with the WorkWave MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

WorkWave MCP Tools for Cursor (10)

These 10 tools become available when you connect WorkWave to Cursor via MCP:

01

get_account_details

Retrieves details for a specific customer account

02

get_api_health

Checks the health and connectivity of the WorkWave API integration

03

get_employee_profile

Retrieves profile details for a specific employee

04

get_order_details

Retrieves details for a specific service order

05

list_field_employees

Lists technicians and field staff registered in WorkWave

06

list_field_service_accounts

Lists customer accounts in the WorkWave Service platform

07

list_service_equipment

Lists managed equipment and assets used in field service

08

list_service_locations

Lists physical service locations and job sites

09

list_service_orders

Lists service orders and work requests

10

update_order_status

g. mark as Pending, InProgress, or Completed). Updates the lifecycle status of a service order

Example Prompts for WorkWave in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with WorkWave immediately.

01

"List all active service orders in WorkWave."

02

"Update order #ORD-101 status to 'InProgress'."

03

"Find the profile for technician ID 'tech-555'."

Troubleshooting WorkWave MCP Server with Cursor

Common issues when connecting WorkWave to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

WorkWave + Cursor FAQ

Common questions about integrating WorkWave MCP Server with Cursor.

01

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

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

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

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.

Connect WorkWave to Cursor

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.