IBM MAS Work Order MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@IBM MAS Work Order MCP Server Show me all open work orders for PUMP-003"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
IBM MAS Work Order MCP Server
Connects Claude directly to your IBM Maximo Application Suite (MAS) so you can chat about live work order data, run analysis, and query maintenance history conversationally.
What Claude can do once connected
Ask Claude... | What happens |
"Show me all open work orders for PUMP-003" | Live API call to MAS, returns real data |
"What's my PM compliance for Q3?" | Fetches PM WOs, calculates on-time % |
"Which assets had the most breakdowns this year?" | Failure analysis across CM/EM WOs |
"What's the cost overrun on WO-10031?" | Pulls actual vs estimated costs |
"Show me the backlog for MechTeamA" | Filtered open WOs by crew |
"Are there any overdue work orders?" | Finds WOs past schedfinish still open |
"Approve work order WO-10045" | Updates status in MAS (with your confirmation) |
Related MCP server: i3X-MCP-Server
Setup
1. Install dependencies
npm install2. Configure environment variables
Create a .env file or export these before running:
# Your MAS server URL (no trailing slash)
MAS_HOST=https://your-mas-instance.example.com
# Authentication — use API key (preferred) OR username/password
MAS_APIKEY=your-api-key-here
# OR basic auth:
MAS_USERNAME=maximo-user
MAS_PASSWORD=maximo-password
# Optional: use lean JSON (smaller responses, recommended)
MAS_LEAN=1Getting a MAS API key: Go to MAS → Security → API Keys → Generate Key
3. Add to Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"ibm-mas": {
"command": "node",
"args": ["/full/path/to/mas-mcp-server/src/index.js"],
"env": {
"MAS_HOST": "https://your-mas-instance.example.com",
"MAS_APIKEY": "your-api-key-here",
"MAS_LEAN": "1"
}
}
}
}Then restart Claude Desktop. You'll see a 🔌 icon confirming the MCP server is connected.
4. Add to Claude Code (alternative)
claude mcp add ibm-mas -- node /full/path/to/mas-mcp-server/src/index.jsSet env vars in your shell before running Claude Code.
Available Tools
Tool | Description |
| Query WOs with filters: status, type, asset, crew, dates, priority |
| Full detail on a single WO including labor/materials |
| All WOs for an asset + MTTR calculation |
| Current open WO backlog with total estimated hours |
| WOs past their scheduled finish date, still open |
| PM WOs in a period with on-time completion % |
| CM/EM breakdown by failure code and asset |
| Actual vs estimated costs with variance % |
| Search assets by number, description, or location |
| Open WO count and hours by crew |
| Change WO status in MAS (approve, start, complete) |
Requirements
Node.js 18+
IBM MAS 8.x or 9.x (Maximo 7.6.1+ also works)
OSLC API enabled on your MAS instance
Network access from the machine running this server to your MAS host
Firewall / VPN note
This server runs locally on your machine and makes outbound HTTPS calls to your MAS host. If MAS is on a private network, run this server from a machine inside that network or connected via VPN.
Available Tools
11 toolsget_assetsA
Search for assets in MAS — get asset details, location, status, and description. Useful for looking up asset numbers before querying work orders.
Inputs: limit, search, status, location.
get_asset_work_historyA
Get the complete maintenance history for a specific asset — all work orders ever raised against it, sorted by date. Great for trend analysis, MTTR, and failure pattern identification.
Inputs: assetnum (required), limit.
get_cost_analysisA
Fetch completed work orders with actual vs estimated costs to calculate cost variance, overruns, and total maintenance spend in a period.
Inputs: limit, date_to, worktype, date_from.
get_crew_workloadB
Get a summary of open work orders grouped by crew to assess workload distribution and backlog per team.
Inputs: date_to, date_from.
get_failure_analysisA
Fetch corrective and emergency work orders with failure codes to analyse breakdown patterns, most common failure types, and assets with repeated failures.
Inputs: limit, date_to, assetnum, date_from.
get_open_backlogA
Fetch all open (not completed/closed/cancelled) work orders — the current maintenance backlog. Useful for workload planning and identifying overdue WOs.
Inputs: crew, limit, worktype.
get_overdue_work_ordersA
Fetch work orders where the scheduled finish date has passed but the WO is still open. Essential for SLA tracking.
Inputs: limit.
get_pm_complianceC
Fetch preventive maintenance (PM) work orders in a date range and calculate compliance — how many were completed on time vs overdue.
Inputs: limit, date_to, location, date_from.
get_work_order_detailA
Get full details for a single work order by WO number, including labor records, materials, costs, failure codes, and all dates.
Inputs: wonum (required).
get_work_ordersA
Fetch work orders from IBM MAS with flexible filters. Use this to query open WOs, filter by status, work type, asset, crew, date range, or priority. Returns full WO details including costs, dates, and failure codes.
Inputs: crew, limit, search, status, +6 more.
update_work_order_statusA
Update the status of a work order in MAS (e.g. approve a WO, mark as in progress). Use with caution — this writes to your live MAS system.
Inputs: wonum (required), status (required), memo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools have a clear analytical purpose, but several overlap: get_open_backlog and get_overdue_work_orders can both be reproduced via get_work_orders filters, and get_asset_work_history overlaps with get_work_orders filtered by asset. Descriptions help differentiate intent, but the boundaries are not crisp.
All tools follow a consistent verb_noun snake_case pattern: get_* for reads and update_work_order_status for writes. No mixed conventions, no vague verbs.
11 tools is well within the ideal 3-15 range. Each tool addresses a specific maintenance analysis or work order query need without feeling bloated.
The read/analysis surface is comprehensive (compliance, cost, failure, backlog, history), but write operations are limited to status updates — creating work orders, closing them, or editing non-status fields are missing. This is a notable gap for a work order server.
Maintenance
Related MCP Connectors
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Manage your IoT device fleet directly from Claude. Create device templates with datastreams and events, provision new devices, read live sensor data, and control outputs. The Blynk connector integrates with the Blynk IoT platform, enabling direct configuration and monitoring of connected devices and infrastructure.
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Related MCP Servers
- AlicenseNot gradedqualityCmaintenancehe Maximo MCP Server bridges AI agents (Claude, Cursor, Antigravity) with your IBM Maximo environment. It empowers your AI to autonomously discover Object Structures (APIs), inspect schemas, and query live data via OSLC. Instead of hallucinating field names, the AI validates queries instantly and ca73 npm11Apache 2.0
- AlicenseAqualityDmaintenanceBridges Claude (or any MCP client) to manufacturing data via the i3X standard, enabling natural language queries about equipment status, hierarchy, and historical trends.122MIT
- FlicenseCqualityDmaintenanceConnects Claude to your Freshservice ITSM instance, enabling management of tickets, changes, assets, knowledge base, and more through natural language.701-
- AlicenseNot gradedqualityDmaintenanceA production-focused integration that brings IBM Maximo Asset Management into AI workflows, enabling natural language interaction with assets, work orders, inventory, and more.3Apache 2.0