Forge reads HTTP / REST and emits the same canonical JSON as every other protocol. No per-vendor parser, no per-vendor schema.
One MCP endpoint serves every protocol adapter: there is no per-protocol URL to configure.
Each links to its own mapping reference with vendor-specific tag shapes.
The fields most commonly emitted by these 23 OEMs. The full schema is open source: FoundryNet/canonical-schema (MIT).
vehicle.brake.air_pressurevehicle.brake.primary_air_pressurevehicle.dtc_descriptionvehicle.engine.fuel_rail_pressurevehicle.engine.intake_manifold_pressurevehicle.engine.oil_pressurevehicle.engine.oil_tempvehicle.tire_pressure_flvehicle.transmission.oil_tempvehicle.turbocharger.rpmvehicle.wheel_speed_flamr.battery.charge
heavy vehicle / off-highway CNC / machine tool autonomous mobile robot industrial robot
Other protocols: BACnet/IP EtherNet/IP J1939 (CAN) MQTT MTConnect Modbus TCP OPC UA PROFINET / S7 ROS 2 (DDS)
operating_hours feed_rate energy_kwh axes.0.temperature_c spindle_speed_rpm axes.0.position_actual axes.0.load_percent spindle_load_pct All fields →