INDIVIDUAL MCP TOOL

ask_maximo

Answer a practical IBM Maximo question from Assetize’s published, source-backed knowledge.

assetize.com.aunone authenticationAvailability not checked

LIVE ENDPOINT

https://assetize.com.au/mcp

No auth detected

Connect to this endpoint to inspect the live schema for ask_maximo and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.assetize-maximo]
url = "https://assetize.com.au/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "assetize-maximo": {
      "type": "http",
      "url": "https://assetize.com.au/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: assetize-maximo
Remote MCP URL: https://assetize.com.au/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "assetize-maximo": {
      "url": "https://assetize.com.au/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "assetize-maximo": {
      "type": "http",
      "url": "https://assetize.com.au/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "assetize-maximo",
  "transport": "streamable-http",
  "url": "https://assetize.com.au/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

search_records — Fast keyword search over published Assetize knowledge records.
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 changes, API changes, gotchas), fixes/APARs since, and newly announced capability — the last two reported as context only, never scored as upgrade work.
maximo_changelog — The dated, source-cited log of what changed across IBM Maximo / MAS 9.
change_watch — The curated feed of genuinely material IBM Maximo / MAS 9.
list_gotchas — Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version.
records_by_version — Every published record scoped to a given Maximo version or family (e.