Bring Work Orders
to CrewAI
Learn how to connect MaintainX to CrewAI 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 CrewAI?
When paired with CrewAI, MaintainX becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call MaintainX tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
MaintainX in CrewAI
MaintainX and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MaintainX to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.