Bring Work Orders
to VS Code Copilot
Learn how to connect MaintainX to VS Code Copilot and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the MaintainX MCP Server?
Connect your MaintainX workspace to any AI agent to automate your maintenance operations and asset management. This MCP server enables your agent to list work orders, retrieve detailed asset metadata, update task statuses, and monitor facility locations directly from natural language interfaces.
What you can do
- Work Order Oversight — List all maintenance tasks and retrieve detailed statuses, priorities, and descriptions
- Asset Management — Monitor equipment and machinery health by retrieving complete metadata and associated work orders
- Status Automation — Update the progress of tasks (e.g., to 'Done' or 'In Progress') programmatically from your conversation
- Facility Tracking — List and inspect physical sites and areas where your assets and team members reside
- User Coordination — List team members and manage assignees for specific maintenance tasks effortlessly
How it works
1. Subscribe to this server
2. Enter your MaintainX API Key (Bearer Token)
3. Start managing your operations from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Maintenance Managers — Monitor operational performance and update task statuses via simple natural language commands
- Facility Coordinators — Quickly audit asset locations and team assignments without opening the portal
- Operations Developers — Integrate maintenance data and task automation directly into your custom internal tools
Built-in capabilities (8)
Requires title. Create a new maintenance work order
Get metadata for a specific asset
Get details for a specific work order
List facility locations
List all physical assets and equipment
Use optional params for filtering. List all work orders
List all users in the MaintainX account
g., "DONE", "IN_PROGRESS"). Change the status of a work order
Why VS Code Copilot?
GitHub Copilot Agent mode brings MaintainX data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
MaintainX in VS Code Copilot
MaintainX and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MaintainX to VS Code Copilot 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 MaintainX in VS Code Copilot
The MaintainX 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 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot 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
MaintainX for VS Code Copilot
Every tool call from VS Code Copilot to the MaintainX MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my MaintainX API Key?
Log in to your MaintainX account as an admin, navigate to Settings > Integrations, and click 'New Key' to generate your token. Your token is encrypted at rest and injected securely at runtime.
What status codes should I use for work orders?
Common status codes include 'OPEN', 'IN_PROGRESS', 'DONE', and 'ON_HOLD'. Use the update_work_order_status tool with these values.
Can I see which asset is linked to a work order?
Yes, when using list_maintenance_orders, you can provide params with include=assets to see linked equipment names in the results.
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.
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.
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.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
