IBM MAS Work Order MCP Server
Related Servers
Alternatives to IBM MAS Work Order MCP Server
No user-submitted related servers found.
Related Servers
- 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
- FlicenseCqualityDmaintenanceConnects Claude to your Freshservice ITSM instance, enabling management of tickets, changes, assets, knowledge base, and more through natural language.701-
- AlicenseAqualityDmaintenanceBridges Claude (or any MCP client) to manufacturing data via the i3X standard, enabling natural language queries about equipment status, hierarchy, and historical trends.127 npm2MIT
- AlicenseNot gradedqualityDmaintenancehe 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 ca29 npm9Apache 2.0
- FlicenseBqualityDmaintenanceConnects Claude to Jira, allowing users to query tasks, log work, add comments, and execute JQL queries through conversational AI.22-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with ServiceNow instances through the ServiceNow API, supporting record management, service catalog operations, change management, and more via natural language.MIT
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.