ITWorx MCP Hub integration

Objective

Publish four read-only MobilityOps capabilities through the existing central ITWorx MCP Hub. MobilityOps does not host MCP transport itself.

Provider registration

provider ID: mobilityops
API base: configurable internal MobilityOps API URL
authentication: scoped service token
mode: read-only
required scope: mobilityops.read

Tools

The machine-readable definitions are in contracts/mcp-tools.json.

mobilityops_get_operations_summary
mobilityops_list_attention_vehicles
mobilityops_get_vehicle_details
mobilityops_search_knowledge

Routing

Operational tools:

AI client -> MCP Hub -> MobilityOps provider API

Knowledge tool:

Preferred:

AI client -> MCP Hub -> RAGcore workspace mobilityops

If the Hub requires a single provider boundary, route through a narrow MobilityOps knowledge façade that calls RAGcore. Do not duplicate retrieval logic.

Restrictions

Do not expose:

generic SQL;
arbitrary URL fetching;
arbitrary shell commands;
return registration;
customer merge;
booking or vehicle mutation;
secrets or raw service configuration.

Audit

The Hub owns central tool-call audit. MobilityOps also records service requests that reach its provider APIs with tool name, correlation ID, client/service identity and result status.

1.3 KiB Raw Blame History