Categories › Productivity & Office › Notes, docs & knowledge bases
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
Remote server: your requests and data go to assetize.com.au. Claude Code: claude mcp add --transport http assetize-ibm-maximo-knowledge https://assetize.com.au/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
ask_maximo — Answer a practical IBM Maximo question from Assetize’s published, source-backed knowledge. The answer cites its evidence ([R#] markers with search_records — Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.lookup_error_code — Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).get_record — Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.compare_maximo_versions — Compare two Maximo versions/eras and get a cited upgrade-impact report per functional area: changes to absorb (deprecations, behaviour changmaximo_changelog — The dated, source-cited log of what changed across IBM Maximo / MAS 9.x (9.1 onward): deprecations, behaviour changes, API/fixes, security, change_watch — The curated feed of genuinely material IBM Maximo / MAS 9.x changes — security, upgrades, deprecations, releases, behaviour and migration brlist_gotchas — Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assrecords_by_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>.behaviour_history — Historical, lifecycle, behaviour-change, deprecation, architecture and API records — the "how did this get here / when does it end" archaeolsupport_lifecycle — IBM Maximo / MAS support-lifecycle facts: end-of-support / Extended Support transitions and the 2026/2027 deadlines, drawn from source-backecorpus_stats — Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence ittest_automation_script_evidence — Statically check a WORKORDER Object launch point Automation Script (Jython or JavaScript) against one release lens's real MXAPIWODETAIL dictupgrade_plan — 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 suppoupgrade_checklist — The phased checklist (before / during / after) for one Maximo move. Every item is CITED — its published records are resolved against the corfixes_gained — 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 functionaldeprecation_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), andlifecycle_dates — End-of-support, Extended Support and Dual Support dates for Maximo and MAS as structured rows: product, version, milestone, ISO date, days rmaximo_mobile — Researched IBM statements about Maximo Mobile, by topic: what it is, the shell and Graphite-app architecture, device requirements (OS levelsNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.