Agents Index

Assetize — IBM Maximo knowledge

Online

Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.

Visit publisherConnectJSON

What it can do: 19 tools

  • ask_maximoAnswer 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 neve
  • search_recordsFast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
  • lookup_error_codeFind published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
  • get_recordFetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
  • compare_maximo_versionsCompare 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 — t
  • maximo_changelogThe 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-
  • change_watchThe 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
  • list_gotchasKnown traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
  • records_by_versionEvery 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_historyHistorical, 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.
  • support_lifecycleIBM 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.
  • corpus_statsCoverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
  • test_automation_script_evidenceStatically 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/setValu
  • upgrade_planOne 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 sa
  • upgrade_checklistThe 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 VER
  • fixes_gainedEvery 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.
  • deprecation_registerWhat 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
  • lifecycle_datesEnd-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 versi
  • maximo_mobileResearched 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 (store

Connect it

Claude Code
claude mcp add --transport http assetize-ibm-maximo-knowledge https://assetize.com.au/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://assetize.com.au/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "assetize-ibm-maximo-knowledge": {
      "url": "https://assetize.com.au/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "assetize-ibm-maximo-knowledge": {
      "type": "http",
      "url": "https://assetize.com.au/mcp"
    }
  }
}

Questions

What does Assetize — IBM Maximo knowledge do?

Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle. It exposes 19 tools to AI assistants.

What tools does Assetize — IBM Maximo knowledge provide?

19 tools, including ask_maximo, search_records, lookup_error_code, get_record, compare_maximo_versions, maximo_changelog, change_watch, list_gotchas, records_by_version, behaviour_history, support_lifecycle, corpus_stats….

How do I connect Assetize — IBM Maximo knowledge to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://assetize.com.au/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Assetize — IBM Maximo knowledge require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Assetize — IBM Maximo knowledge online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Assetize — IBM Maximo knowledge?

assetize.com.au. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Developer Tools