behaviour_history — Assetize — IBM Maximo knowledge MCP Tool
behaviour_history
(behaviour history) is one of 19 tools on the
Assetize — IBM Maximo knowledge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call behaviour_history from your client
- Claude Code Assetize — IBM Maximo knowledge behaviour_history run in your project directory
- Claude Desktop Assetize — IBM Maximo knowledge behaviour_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Assetize — IBM Maximo knowledge behaviour_history ~/.cursor/mcp.json
- VS Code Assetize — IBM Maximo knowledge behaviour_history .vscode/mcp.json
- Zed Assetize — IBM Maximo knowledge behaviour_history ~/.config/zed/settings.json
- Windsurf Assetize — IBM Maximo knowledge behaviour_history ~/.codeium/windsurf/mcp_config.json
- Cline Assetize — IBM Maximo knowledge behaviour_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Assetize — IBM Maximo knowledge behaviour_history ~/.gemini/settings.json
- Grok Assetize — IBM Maximo knowledge behaviour_history .mcp.json (in your project root)
- ChatGPT Assetize — IBM Maximo knowledge behaviour_history Settings → Connectors → Advanced → Developer mode
- Claude.ai Assetize — IBM Maximo knowledge behaviour_history Settings → Connectors → Add custom connector
- LangChain Assetize — IBM Maximo knowledge behaviour_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http maximo https://assetize.com.au/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.