Retrieve the Active Operational Dataset from OTBR in hex format: ot-ctl dataset active -x (or via the OTBR REST API at /api/v1/node/dataset/active)
Ensure the commissioning host running chip-tool is on the same LAN as the OTBR so it can reach Thread devices over the border router
Put the Matter device into BLE advertising mode (factory reset or hold the pairing button); confirm it is advertising with a BLE scanner
Run: chip-tool pairing ble-thread <node_id> hex:<operational_dataset> <setup_pin_code> <discriminator> — chip-tool pairs over BLE and provisions the Thread network credentials
Wait for commissioning to complete; chip-tool logs should show 'Device commissioning completed with success'
Send a test command (e.g., chip-tool onoff toggle <node_id> 1) to confirm the device is reachable over Thread via the border router
Known gotchas
The setup PIN code and discriminator are printed on the device or encoded in its QR code; verify them before starting commissioning to avoid failed attempts
chip-tool must be run on a host with a Bluetooth adapter; on headless servers, a BLE dongle may be needed
If commissioning fails with a timeout, confirm that the Thread dataset is for the correct network and that the OTBR has an active Leader role
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp