MCP Server

Assetize — IBM Maximo knowledge

au.com.assetize/maximo

What this MCP does

Provides cited IBM Maximo and MAS documentation, troubleshooting, lifecycle, change, deprecation, upgrade-planning, and automation-script evidence tools.

ask_maximo
Ask a Maximo question (evidence-cited)
Answer a practical IBM Maximo question from Assetize’s published, source-backed knowledge. The answer cites its evidence ([R#] markers with source URLs) and DECLINES when the published record cannot support one — it never guesses. Best for how-to, troubleshooting, version-behaviour and error questions.
Input schema
{'type': 'object', 'required': ['question'], 'properties': {'version': {'type': 'string', 'description': 'Optional version scope, e.g. "9.2", "8.11", "7.6.1".'}, 'question': {'type': 'string', 'maxLength': 2000, 'minLength': 3, 'description': 'The Maximo question, in plain language.'}}, 'additionalProperties': False}
behaviour_history
Maximo behaviour & lifecycle history
Historical, lifecycle, behaviour-change, deprecation, architecture and API records — the "how did this get here / when does it end" archaeology. Same data as assetize.com.au/archaeology.
Input schema
{'type': 'object', 'properties': {'limit': {'type': 'number', 'description': 'Max results (default 30, max 100).'}, 'version': {'type': 'string', 'description': 'Optional version filter, e.g. "9.2".'}}, 'additionalProperties': False}
change_watch
Curated Maximo Change Watch
The curated feed of genuinely material IBM Maximo / MAS 9.x changes — security, upgrades, deprecations, releases, behaviour and migration breaks. Each carries What Changed / Why It Matters, previous behaviour, a version comparison, a clearly-labelled Assetize interpretation (never presented as IBM’s), the IBM sources, and the corpus records that grounded it. Pass a slug for one change in full; omit it to list, optionally filtered by category. Same data as assetize.com.au/change-watch.
Input schema
{'type': 'object', 'properties': {'slug': {'type': 'string', 'description': 'A change slug for the full record. Omit to list.'}, 'limit': {'type': 'number', 'description': 'Max items when listing (default 30, max 60).'}, 'category': {'type': 'string', 'description': 'Filter: SECURITY|UPGRADE|DEPRECATION|RELEASE|BEHAVIOUR|MIGRATION|INTEGRATION|SUPPORT.'}}, 'additionalProperties': False}
compare_maximo_versions
Compare two Maximo versions
Compare two Maximo versions/eras and get a cited upgrade-impact report per functional area: changes to absorb (deprecations, behaviour changes, API changes, gotchas), fixes/APARs since, and newly announced capability — the last two reported as context only, never scored as upgrade work. Same reviewed, source-backed comparison and ranking as assetize.com.au/compare. Accepts either a version label ("7.6.1.3", "9.2") or bucket id ("9-2"). Known buckets: 7.6.1.3, 7.6.x (classic Maximo 7.6/7.6.1/7.6.1.x), 8.x (Maximo Application Suite 8), 9.0, 9.1, 9.2.
Input schema
{'type': 'object', 'required': ['from', 'to'], 'properties': {'to': {'type': 'string', 'description': 'Target version, e.g. "9.2".'}, 'from': {'type': 'string', 'description': 'Starting version, e.g. "7.6.1.3".'}}, 'additionalProperties': False}
corpus_stats
Assetize corpus coverage
Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
Input schema
{'type': 'object', 'properties': {}, 'additionalProperties': False}
deprecation_register
Deprecation, removal and rename register
What was deprecated, removed or renamed in Maximo / MAS, in which version, what IBM says replaces it (blank when IBM has not named one), and the published records that say so. Curated; rows publish only on evidence. Same data as assetize.com.au/upgrade/deprecations.
Input schema
{'type': 'object', 'properties': {'kind': {'type': 'string', 'description': 'Optional: DEPRECATION, REMOVAL or RENAME.'}}, 'additionalProperties': False}
fixes_gained
Fixes and security changes a move carries
Every FIX and SECURITY record the 9.x change log holds for the releases inside a move (the 9.x log starts at 9.1). Optionally one functional area. Counted, never scored as upgrade weight.
Input schema
{'type': 'object', 'required': ['from', 'to'], 'properties': {'to': {'type': 'string', 'description': 'Target release, e.g. "9.2".'}, 'area': {'type': 'string', 'description': 'Optional functional area, e.g. "WORK_ORDERS".'}, 'from': {'type': 'string', 'description': 'Source release, e.g. "9.1".'}, 'limit': {'type': 'number', 'description': 'Max entries per section (default 40, max 200).'}}, 'additionalProperties': False}
get_record
Get a full record with sources
Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
Input schema
{'type': 'object', 'required': ['slug'], 'properties': {'slug': {'type': 'string', 'description': 'Record slug from search_records / lookup_error_code results.'}}, 'additionalProperties': False}
lifecycle_dates
Structured Maximo support dates
End-of-support, Extended Support and Dual Support dates for Maximo and MAS as structured rows: product, version, milestone, ISO date, days remaining, and the IBM page each comes from. Optionally scope by product or version. Same data as assetize.com.au/upgrade/deadlines.
Input schema
{'type': 'object', 'properties': {'product': {'type': 'string', 'description': 'Optional product substring, e.g. "Application Suite" or "Asset Management".'}, 'version': {'type': 'string', 'description': 'Optional version, e.g. "8.11", "7.6.1", "9.0".'}}, 'additionalProperties': False}
list_gotchas
Maximo gotchas & upgrade traps
Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
Input schema
{'type': 'object', 'properties': {'limit': {'type': 'number', 'description': 'Max results (default 30, max 100).'}, 'version': {'type': 'string', 'description': 'Optional version, e.g. "9.2".'}}, 'additionalProperties': False}
lookup_error_code
Look up a Maximo error code
Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
Input schema
{'type': 'object', 'required': ['code'], 'properties': {'code': {'type': 'string', 'description': 'The error/fix code, e.g. "BMXAA4214E".'}}, 'additionalProperties': False}
maximo_changelog
Maximo 9.x change log
The dated, source-cited log of what changed across IBM Maximo / MAS 9.x (9.1 onward): deprecations, behaviour changes, API/fixes, security, gotchas, upgrades, lifecycle and releases. Only real change records (never data-dictionary noise) and nothing the curator demoted. Same data as assetize.com.au/changelog. Optionally filter by version ("9.1", "9.2") and/or type.
Input schema
{'type': 'object', 'properties': {'type': {'type': 'string', 'description': 'Filter to one change type: DEPRECATION, BEHAVIOUR_CHANGE, FIX, SECURITY, GOTCHA, UPGRADE, LIFECYCLE, RELEASE.'}, 'limit': {'type': 'number', 'description': 'Max entries (default 200, max 1000).'}, 'version': {'type': 'string', 'description': 'Filter to a 9.x line, e.g. "9.2". Omit for all of 9.x.'}}, 'additionalProperties': False}
maximo_mobile
What IBM says about Maximo Mobile
Researched IBM statements about Maximo Mobile, by topic: what it is, the shell and Graphite-app architecture, device requirements (OS levels, memory, WebView2, ARCore, shared devices), getting the app onto devices (stores, MSIX, QR server URL, MDM), login and shared devices, data sync and attachments, administration (Mobile Configuration app, properties), the apps release by release (8.11, 9.0, 9.1, 9.2), push notifications, and coming from Maximo Anywhere or 7.6.1. Every fact carries IBM's verbatim sentence, page and read date. Scope by release and/or topic. Same data as assetize.com.au/mobile. For fixes and gotchas use search_records.
Input schema
{'type': 'object', 'properties': {'topic': {'type': 'string', 'description': 'Optional topic: what, architecture, devices, deploy, auth, sync, admin, apps, notifications, classic.'}, 'version': {'type': 'string', 'description': 'Optional Maximo Mobile release: "8.11", "9.0", "9.1" or "9.2". Facts that hold for every release are always included.'}}, 'additionalProperties': False}
records_by_version
What Assetize covers for a version
Every published record scoped to a given Maximo version or family (e.g. "9.2", "7.6.1"). Same data as assetize.com.au/maximo/<version>.
Input schema
{'type': 'object', 'required': ['version'], 'properties': {'limit': {'type': 'number', 'description': 'Max results (default 40, max 200).'}, 'version': {'type': 'string', 'description': 'Version label or family, e.g. "9.2".'}}, 'additionalProperties': False}
search_records
Search published Maximo records
Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
Input schema
{'type': 'object', 'required': ['query'], 'properties': {'limit': {'type': 'number', 'description': 'Max results, 1-25 (default 10).'}, 'query': {'type': 'string', 'description': 'Keywords or an exact identifier (MXAPI..., BMX..., module name).'}, 'version': {'type': 'string', 'description': 'Optional version label or family filter, e.g. "9.2".'}}, 'additionalProperties': False}
support_lifecycle
Maximo support & end-of-support dates
IBM Maximo / MAS support-lifecycle facts: end-of-support / Extended Support transitions and the 2026/2027 deadlines, drawn from source-backed lifecycle records and the curated Change Watch. Optionally scope to a version.
Input schema
{'type': 'object', 'properties': {'limit': {'type': 'number', 'description': 'Max results (default 30).'}, 'version': {'type': 'string', 'description': 'Optional version, e.g. "8.11", "9.0".'}}, 'additionalProperties': False}
test_automation_script_evidence
Check a WORKORDER Automation Script against a Maximo/MAS lens (Automation Script Test Harness)
Statically check a WORKORDER Object launch point Automation Script (Jython or JavaScript) against one release lens's real MXAPIWODETAIL dictionary. Extracts every attribute the script references via mbo.getString/setValue/isNull/getInt/getDate/getBoolean, then reports which ones the named lens has evidence for. Static evidence only — it does not run the script. A missing attribute is reported NOT_ASSESSED, never claimed as a runtime failure; for a real pass/fail/skip verdict, run the CLI (mvn verify) or the browser runner at assetize.com.au/test-stubs/automation-scripts. Lenses: 761 (Maximo 7.6.1), mas811 (MAS 8.11), mas90 (MAS 9.0), mas91 (MAS 9.1), mas92 (MAS 9.2).
Input schema
{'type': 'object', 'required': ['source', 'lens'], 'properties': {'lens': {'enum': ['761', 'mas811', 'mas90', 'mas91', 'mas92'], 'type': 'string', 'description': 'The target release lens.'}, 'source': {'type': 'string', 'maxLength': 65536, 'minLength': 1, 'description': 'The Automation Script source — Jython or JavaScript, a WORKORDER Object launch point. Up to 64 KiB.'}}, 'additionalProperties': False}
upgrade_checklist
Phased upgrade checklist for a move
The phased checklist (before / during / after) for one Maximo move. Every item is CITED — its published records are resolved against the corpus on this call and an item whose records are not published is dropped — or VERIFY, a level-dependent question to settle against IBM. Optionally one phase.
Input schema
{'type': 'object', 'required': ['from', 'to'], 'properties': {'to': {'type': 'string', 'description': 'Target release, e.g. "9.2".'}, 'from': {'type': 'string', 'description': 'Source release, e.g. "8.11".'}, 'phase': {'type': 'string', 'description': 'Optional: BEFORE, DURING or AFTER.'}}, 'additionalProperties': False}
upgrade_plan
Plan a Maximo move (Upgrade Desk)
One Maximo move from an earlier catalogue release to a later one (7.6.1, 8.11, 9.0, 9.1, 9.2), composed from the published record: the support clock on the source release, the staged route (IBM's n-1 policy), what IBM says about the move (route, platform, database, Java, users, add-ons, reports; each with IBM's words and page), the few items only the customer's own system can answer, break-class changes (deprecations, behaviour changes) and landmines (upgrade notes, gotchas) in range from the 9.x change log, fix and security counts, the deprecation-register rows touching the range, and the curated Change Watch entries. Every item links its record or IBM page. Same composition as assetize.com.au/upgrade/<from>/<to>.
Input schema
{'type': 'object', 'required': ['from', 'to'], 'properties': {'to': {'type': 'string', 'description': 'Target release: "8.11", "9.0", "9.1", "9.2".'}, 'from': {'type': 'string', 'description': 'Source release: "7.6.1", "8.11", "9.0", "9.1".'}}, 'additionalProperties': False}
Added
maximo_mobile
Sept. 27, 2026, 2:40 a.m.
Added
lifecycle_dates
Sept. 27, 2026, 2:40 a.m.
Added
deprecation_register
Sept. 27, 2026, 2:40 a.m.
Added
fixes_gained
Sept. 27, 2026, 2:40 a.m.
Added
upgrade_checklist
Sept. 27, 2026, 2:40 a.m.
Added
upgrade_plan
Sept. 27, 2026, 2:40 a.m.
Added
test_automation_script_evidence
Sept. 27, 2026, 2:40 a.m.
Added
corpus_stats
Sept. 27, 2026, 2:40 a.m.
Added
support_lifecycle
Sept. 27, 2026, 2:40 a.m.
Added
behaviour_history
Sept. 27, 2026, 2:40 a.m.
Added
records_by_version
Sept. 27, 2026, 2:40 a.m.
Added
list_gotchas
Sept. 27, 2026, 2:40 a.m.
Added
change_watch
Sept. 27, 2026, 2:40 a.m.
Added
maximo_changelog
Sept. 27, 2026, 2:40 a.m.
Added
compare_maximo_versions
Sept. 27, 2026, 2:40 a.m.
Added
get_record
Sept. 27, 2026, 2:40 a.m.
Added
lookup_error_code
Sept. 27, 2026, 2:40 a.m.
Added
search_records
Sept. 27, 2026, 2:40 a.m.
Added
ask_maximo
Sept. 27, 2026, 2:40 a.m.