ToolBB-0158

BREMA: an agent commissions KNX devices through a stick that is its own MCP server

BREMA is busware firmware for its TUL KNX stick that answers MCP over plain HTTP on the local network. An agent can address a factory-fresh KNX actuator, write its tables and parameters and add it to Home Assistant without ETS. The README says the commissioning example ran on hardware but shows no photos or logs.

Open original source github.com · Dirk Tostmann

Claimed
Why this evidence label?

README states the KNX commissioning example ran on real hardware; no photos, video or logs are shown.

How we check entries
Preview image for BREMA: an agent commissions KNX devices through a stick that is its own MCP server
The source's own preview image, from github.com.

Briefing

BREMA moves device knowledge out of compiled firmware into descriptions stored on the stick, so supporting a new device means loading a file instead of waiting for a release. A language model writes those descriptions from structured facts, and a deterministic gate replays each one against captured frames before it goes live. For KNX, the manufacturer's product file is still the input.

The MCP tools are generated from the firmware's own command registry, and mutating commands default to dry runs. The stick pairs an ESP32-C6 with an NCN5130 bus transceiver. The firmware runs only on busware TUL hardware, paired to each stick, because the KNX pins differ per product. The repository holds documentation, not firmware source.

From the GitHub API

Repository facts

Repository facts for tostmann/brema, from the GitHub API
Repositorytostmann/brema
Stars0
Last push14 Aug 2026 2 mo ago

Tags

Report a problem with this entry