Point the MCP server at an i3X instance. Required before any data tool will work (unless I3X_BASE_URL was set in the env). Validates by calling /info on the target. Switching connections at any time is fine — call this again.

Returns whether an i3X connection is active, the baseUrl, auth scheme, and catalog snapshot.

Returns the i3X server's capabilities, version, and supported features (query/update/subscribe).

Fuzzy/substring search over the cached object catalog. Use this to find equipment, sensors, or processes by name. Returns elementId, displayName, type, and parent path.

Returns top-level objects in the i3X hierarchy (no parent). Good entry point for unfamiliar plants.

Rebuilds the local object/type catalog from the i3X server.

Detailed info for one or more objects: type, parent, composition flag, declared relationships.

Latest value (with quality and timestamp) for one or more objects. Set maxDepth>1 to include composed sub-components. Values are enriched with engineering units when the ObjectType schema declares them.

Historical values over a time range with optional server-side aggregation. Times accept RFC 3339, relative durations ('1h', 'last 30m'), 'now', 'today', or 'yesterday'. For long ranges use aggregation='avg'|'min'|'max'|'count' with a bucket like '5m' or '1h'.

Objects related to the given ones via the i3X relationship graph. If relationshipType omitted, groups by type.

Returns the JSON Schema and per-field units for an ObjectType.

Monitor one or more objects for live changes over a bounded duration (max 300s). Creates an i3X subscription internally and cleans it up on exit. Returns per-element summary of all observed changes (count, first, last, min, max).