57 lines
1.3 KiB
Markdown
57 lines
1.3 KiB
Markdown
# 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`.
|
|
|
|
1. `mobilityops_get_operations_summary`
|
|
2. `mobilityops_list_attention_vehicles`
|
|
3. `mobilityops_get_vehicle_details`
|
|
4. `mobilityops_search_knowledge`
|
|
|
|
## Routing
|
|
|
|
Operational tools:
|
|
|
|
```text
|
|
AI client -> MCP Hub -> MobilityOps provider API
|
|
```
|
|
|
|
Knowledge tool:
|
|
|
|
Preferred:
|
|
|
|
```text
|
|
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.
|