Bring Work Orders
to Claude Desktop
Learn how to connect MaintainX to Claude Desktop and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
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 Claude Desktop?
Claude Desktop is the definitive way to connect MaintainX to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
MaintainX in Claude Desktop
MaintainX and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MaintainX to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.