Maintainx
MaintainX is a cloud-based computerized maintenance management system (CMMS) that helps organizations centralize maintenance data, communication, and workflows.
Verdict
Common use cases
- Triage facility issues reported in chat
- Log work order updates without switching apps
- Check asset locations during planning calls
- Create maintenance tickets from incident notes
- Pull team assignments for shift handoffs
Integration
- Vendor
- Maintainx
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
maintainx
Tools
- Create Work Order
This tool creates a new work order in maintainx. it uses the post /api/v1/workorders endpoint. the tool requires a 'title' for the work order and offers several optional parameters including description, priority, duedate, startdate, userid
- Create Work Order Comment
This tool creates a new comment on an existing work order in maintainx. it allows users to add comments for documentation, updates, or communication purposes within a specific work order. it requires a workorderid and the text content of th
- Create Work Request Portal
Creates a new work request portal in maintainx. a work request portal allows users to submit work requests through a dedicated url. the portal can be customized with a title, welcome text, and description placeholder. it can be associated w
- Find Entity
A tool to search and find specific entities within maintainx by specified fields. this tool allows users to search for different types of entities including work orders, users, and locations.
- List Assets
This tool allows users to retrieve a list of all assets in their organization.
- List Categories
This tool retrieves a list of all categories in your maintainx organization. categories are used to organize and classify work orders, assets, and other items in the system. it supports listing the categories with pagination and provides de
- List Locations
This tool retrieves a list of all available locations in the organization's maintainx account. the locations can be physical places where assets are located, work is performed, or maintenance is needed.
- List Teams
This tool retrieves a list of all teams in your maintainx organization.
- List Work Orders
Action to list work orders from maintainx.
- Update Work Order
This tool allows users to update an existing work order in maintainx by modifying specific attributes without affecting other unchanged fields. it requires the workorder id and at least one of the optional parameters (title, description, or
- Update Work Order Status
This tool allows users to update the status of a specific work order in maintainx. it is focused specifically on status updates, making it more streamlined than the comprehensive 'update work order' action which allows updating multiple fie
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select MaintainX from the list. 3. Log into your MaintainX account, go to Settings > API, and generate a new API key with read and write permissions. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Switchy will verify the key by fetching your organization's team list. 6. Once connected, open any Space and type '@MaintainX list teams' to confirm the integration responds. 7. To create a work order, @mention MaintainX and describe the task in plain language — the AI will map your request to the correct tool and parameters. 8. Check the MaintainX activity log to see new work orders or comments appear in real time.
What teammates see: by default, memories from Maintainx are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create HVAC Work Order
@MaintainX create a work order titled 'HVAC unit 3B not cooling' with description 'Reported by front desk, temperature reading 78F in zone 3, needs immediate inspection'.Open in a Space →
List All Assets
@MaintainX list all assets in our organization and show their current locations.Open in a Space →
Add Work Order Comment
@MaintainX add a comment to work order #4521 saying 'Technician arrived on site, replacement part ordered, ETA Friday'.Open in a Space →
Find Work Orders by Location
@MaintainX find all work orders for location 'Building A - 2nd Floor' and show their status.Open in a Space →
Check Team Assignments
@MaintainX list all teams and show which members are assigned to each one.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@maintainx list all open work orders for the warehouse location and group them by priority
Found 14 open work orders at the warehouse location. High priority (5): HVAC unit #3 repair, forklift brake inspection overdue, loading dock door malfunction, emergency lighting failure in zone B, compressor leak in cold storage. Medium priority (6): routine conveyor belt maintenance, pallet rack safety audit, floor striping refresh, fire extinguisher inspections, restroom plumbing check, parking lot pothole repair. Low priority (3): break room microwave replacement, signage updates, landscaping trim. All work orders include assigned teams and estimated completion dates.
This example demonstrates the MCP's search and filtering capabilities across work orders. Requires read access to work orders and locations via API key. The MCP returns structured data that the AI can organize and summarize—actual field availability depends on your MaintainX plan tier and custom field configuration.
@maintainx create a work order titled 'Replace air filter in Unit 7' assigned to the HVAC team with high priority and due date next Friday
Created work order WO-8847: 'Replace air filter in Unit 7'. Assigned to HVAC team with high priority. Due date set to Friday, January 17, 2025. The work order is now visible in the HVAC team's queue and will trigger notifications per your team's settings. You can add procedure checklists, attach photos, or link related assets by mentioning this work order ID in follow-up prompts.
This example shows the MCP's ability to create actionable work orders with assignment and scheduling. Requires write permissions on your API key. Side-effect: immediately creates a record in MaintainX and may trigger team notifications. Verify team names and priority levels match your organization's configuration before bulk creation.
@maintainx pull all assets tagged 'critical' and draft a quarterly maintenance schedule based on manufacturer recommendations and past work order history
Retrieved 23 critical assets across 4 locations. Based on manufacturer specs and historical work orders, here's a proposed Q1 maintenance schedule: Week 1—inspect chillers (assets #102, #103) and test backup generators (assets #210, #211). Week 4—replace HVAC filters (assets #305-#312). Week 8—lubricate conveyor systems (assets #401-#405). Week 12—full safety audit on forklifts (assets #501-#507). This schedule staggers high-downtime tasks and aligns with your team's past completion rates of 4-6 work orders per week.
This example highlights the MCP's ability to surface asset data for AI-driven planning. The AI synthesizes asset metadata with work order patterns to propose a schedule—this is illustrative reasoning, not a built-in MaintainX feature. Requires read access to assets and work order history. Always validate manufacturer intervals and team capacity before committing to a schedule.
Use-case deep-dives
When Maintainx MCP fits small facilities ops
A 6-person facilities team managing 3 office locations uses Slack for most coordination but needs to log maintenance issues in Maintainx without context-switching. The MCP works here because the team creates 15-30 work orders a week, mostly reactive (broken HVAC, plumbing leaks, equipment failures). The Create Work Order and List Locations tools let an AI agent file tickets directly from a Slack thread where someone reports a problem, auto-assigning the right location and category. The Find Entity tool helps pull status updates mid-week without opening the Maintainx dashboard. This breaks down if your team runs scheduled preventive maintenance at scale—Maintainx's calendar and recurring task features aren't exposed through the MCP, so you'll still need the web UI for PM workflows. If 80% of your tickets are break-fix and you want faster logging, this MCP saves 10 minutes per ticket.
Why this MCP struggles with asset audits
A retail chain with 12 stores wants to audit equipment (refrigerators, POS systems, security cameras) quarterly and update Maintainx records in bulk. The MCP's List Assets and List Locations tools can pull current inventory, but there's no bulk-update or asset-edit tool exposed—only work order creation. An AI agent can read asset lists and compare them to a spreadsheet, but it can't write changes back to asset records. You'd need to create a work order for each discrepancy and manually resolve it in the Maintainx UI, which defeats the automation goal. This scenario needs either Maintainx's native CSV import or a more complete API wrapper. The MCP is read-heavy by design, so if your use case is 'update 200 asset records after a physical count,' expect to do that work outside the MCP. Stick to reactive ticketing workflows where the MCP shines.
Bridging support tickets and field work orders
A 10-person SaaS company with on-prem hardware at client sites uses Zendesk for support and Maintainx to dispatch field techs. When a customer reports a hardware issue, support needs to create a Maintainx work order without leaving Zendesk or re-typing details. The MCP's Create Work Order and Create Work Order Comment tools let an AI agent parse the Zendesk ticket, extract the client location and problem description, and file a Maintainx ticket in under 30 seconds. The List Teams tool ensures the ticket routes to the right regional crew. This works cleanly if your support volume is under 50 hardware tickets a month—the API key auth is simple, and the 11-tool scope covers the handoff without overwhelming the agent. If you're doing 200+ tickets monthly, you'll want a dedicated Zapier integration or custom middleware. For small teams bridging two systems, this MCP closes the loop fast.
Frequently asked
What does the MaintainX MCP let me do in Switchy?
It connects your MaintainX maintenance operations to AI workflows in Switchy. You can create work orders, add comments to existing tickets, search for assets or locations, and pull team or category lists. The MCP exposes 11 tools covering the core MaintainX objects—work orders, assets, locations, teams—so your AI agents can read maintenance data or trigger new requests without leaving the chat.
Do I need admin access to connect MaintainX?
You need a MaintainX API key, which typically requires admin or elevated permissions in your MaintainX account. Standard users can't generate API keys. Once you have the key, paste it into Switchy's connection flow. The key grants read and write access to work orders, assets, and locations based on your MaintainX role, so check your org's permission model before connecting.
Can the MCP assign work orders to specific technicians?
Not directly through the Create Work Order tool as described. The tool accepts a title and optional parameters like description, but assignee routing isn't listed in the representative tool set. You can create the work order and add a comment with assignment instructions, then handle routing in MaintainX's UI or via a separate API call if your workflow requires it.
Why use this instead of just logging into MaintainX?
Use the MCP when you want AI to handle repetitive maintenance tasks—like auto-creating work orders from Slack alerts, pulling asset lists into a report, or searching for overdue tickets in a daily standup prompt. If you're manually clicking through MaintainX once a week, the web app is faster. If you're doing the same query fifty times or routing requests from other tools, the MCP saves hours.
Who on my team should connect the MaintainX integration?
Whoever owns your MaintainX API keys—usually a facilities manager, operations lead, or IT admin. That person connects it once in Switchy, then any teammate with workspace access can invoke MaintainX tools in their AI chats. The connection is shared, so you don't need every technician to have their own API key or MaintainX admin rights.