INDUSTRIAL ROBOT · CANONICAL DATA MODEL

KUKA canonical data model: connect your KUKA equipment to any AI agent

2,461 confirmed mappings·12 protocols·99% field coverage

Forge turns raw KUKA tags into one clean, governed schema your AI agent already understands. One MCP call, no per-robot integration project.

Try it free: 3 machines, no credit card → See it work →

Paste your KUKA data and see it normalized in 30 seconds. No POC required.

Read-only. Forge reads your KUKA data through standard industrial protocols. Read-only. Your equipment is never at risk.

The problem

Why KUKA data is hard to integrate

KUKA KRC controllers surface state as $-prefixed system variables ($AXIS_ACT, $TORQUE_AXIS) over KUKAVARPROXY or EKI. Expressive but utterly vendor-specific.

Typical KUKA equipment communicates over OPC UA, ROS 2 (DDS), PROFINET / S7, EtherNet/IP. Each firmware revision, model line and integrator names the same physical quantity differently, so every AI or analytics project pays the integration tax again, the tax that cancels 40% of industrial AI deployments before they ship.

The solution

One universal schema for every KUKA robot

Forge resolves KUKA telemetry into Forge's canonical field set, the same 1,027-field canonical schema (366 resolvable from vendor tags today), used across all 47 vendor packs. Point Forge at the robot, pass oem: "kuka", and spindle speed is spindle_speed_rpm whether it came from a KUKA controller or anything else on the floor.

OPC UAROS 2 (DDS)PROFINET / S7EtherNet/IP

99%Field coverage

11Canonical industrial robot fields

3,444Corpus mappings

Field coverage

What Forge resolves for KUKA

Confirmed canonical fields your agent gets from KUKA robots, drawn from Forge's 3,444-mapping corpus:

robot.joint.positionrobot.joint.velocityrobot.joint.effortrobot.joint.currentrobot.joint.temperaturerobot.tcp.poserobot.tcp.speedrobot.tcp.forcerobot.payloadrobot.moderobot.safety.status_bits

Sample normalization

Raw tag in		Canonical field out	Meaning
$AXIS_ACT.A1: 88.2	→	robot.joint.position: 88.2	axis 1 actual angle
$TORQUE_AXIS_1: 12.4	→	robot.joint.effort: 12.4	axis 1 torque
$PAYLOAD.M: 6.0	→	robot.payload: 6.0	payload mass
$PRO_MODE: "AUTO"	→	robot.mode: "AUTO"	program mode

30-second deployment

Add KUKA to your agent with one call

No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live KUKA data:

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'

# normalize raw KUKA telemetry into the universal schema

curl -s https://forge.foundrynet.io/v1/normalize \

-H 'Content-Type: application/json' \

-d '{"data": {"$AXIS_ACT.A1": 88.2, "$TORQUE_AXIS_1": 12.4, "$PAYLOAD.M": 6.0}, "oem": "kuka"}'

{"robot.joint.position": 88.2, "robot.joint.effort": 12.4, "robot.payload": 6.0, "coverage": "100%", "confidence": 0.97}

Unknown tags never get force-mapped. Fields below the confidence floor abstain rather than guess, so your agent never acts on a bad reading.

Start free: Forge API, 3 machines → See the full demo →

Where KUKA fits

Protocols
OPC UA ROS 2 (DDS) PROFINET / S7 EtherNet/IP

Vertical
industrial robot

Other industrial robot vendors
ABB Robotics Universal Robots Fanuc Robotics Yaskawa Motoman Doosan Robotics Epson Robots

Same protocols, other industries
DMG Mori Fanuc Heidenhain Mazak

Also searched as kuka, krc, kr c4, iiwa, eki