Bring Work Orders
to Cline
Learn how to connect MaintainX to Cline 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 Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including MaintainX tool calls without waiting for prompts between steps. Connect 8 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
MaintainX in Cline
MaintainX and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MaintainX to Cline 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 Cline
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 Cline 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 Cline
Every tool call from Cline 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 Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.