Skip to main content
Glama
prajithram

IBM MAS Work Order MCP Server

by prajithram

Related Servers

Alternatives to IBM MAS Work Order MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants directly to IBM Maximo so they can discover APIs, inspect schemas, query live data, generate Carbon UI, and create, update, or act on Maximo records through natural language.
      122 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants directly to IBM Maximo environments to discover APIs, inspect schemas, query live data, generate UI code, and create, update, or act on records through OSLC REST and business workflows.
      122 npm
      Apache 2.0
    • F
      license
      C
      quality
      D
      maintenance
      Connects Claude to your Freshservice ITSM instance, enabling management of tickets, changes, assets, knowledge base, and more through natural language.
      70
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Bridges Claude (or any MCP client) to manufacturing data via the i3X standard, enabling natural language queries about equipment status, hierarchy, and historical trends.
      12
      6 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      he 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 ca
      122 npm
      10
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    ActivitySlowing
    ResponsivenessNo issues