MCP-enabled
Agents use the same jobs as the portal
The portal is the human UI. The backplane is the machine UI. Same VIN, compound, and delivery status — not a second copy of the truth.
Same record
An agent asking for a job sees the same compound, dealer, and POD as the operator workspace and the customer portal.
Scoped access
Tenant-scoped access. Read and write follow the same tenancy rules as the portal — not a shared inbox bot.
Open clients
Cursor, Claude, ChatGPT, or an agent you already run. The protocol is MCP. The product is the job catalog.
Ask for a vehicle, not a shipment
Cargo Chat on ntainers.co answers freight questions in English. RoRo TMS is a different catalog: jobs, not consols. Use the structured job tools when a workflow needs fields.
Human UI → rorotms.com portal. Machine UI → MCP /api/mcp.
object_get({ type: "job", reference: "WDD2130041A123456" }) → compound, dealer, status, POD same record as the RoRo TMS portal