2,500+ MCP servers ready to use
Vinkius

WorkWave MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings WorkWave data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the WorkWave MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using WorkWave

Ask Copilot: "Using WorkWave, help me..."10 tools available

Why Use VS Code Copilot with the WorkWave MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with WorkWave through the Model Context Protocol.

01

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

WorkWave + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the WorkWave MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

WorkWave MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect WorkWave to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting WorkWave to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

WorkWave + VS Code Copilot FAQ

Common questions about integrating WorkWave MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect WorkWave to VS Code Copilot

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