ToolBB-0103

bus-mcp: MCP tools for a Raspberry Pi's CAN, RS-485, I2C, SPI and GPIO

bus-mcp runs on a Raspberry Pi and exposes CAN, CAN-FD, RS-485, UART, I2C, SPI and GPIO as 18 MCP tools. Buses are read-only until writes are enabled for chosen bus kinds. An installer sets up a systemd service with an HTTP endpoint. The README gives a loopback test procedure but no recorded results.

Open original source github.com · Pan Robotics

Claimed
Why this evidence label?

The author describes it but shows no evidence we could check yet.

How we check entries
Preview image for bus-mcp: MCP tools for a Raspberry Pi's CAN, RS-485, I2C, SPI and GPIO
The source's own preview image, from github.com.

Briefing

Each configure tool takes only the fields to change, closes the bus and reopens it with the new settings on the next call. Blocking receives run on a worker thread, so one client can hold a CAN or serial read open while it calls other tools. The installer reuses the apt-packaged bus libraries in its venv and leaves /boot/firmware/config.txt, the CAN bitrate and firewall ports alone. The HTTP endpoint binds to 127.0.0.1 unless --host 0.0.0.0 is passed.

Once writes are on, nothing checks what is sent: a destructive CAN frame reaches the ECU. The README says to use it on bench setups, not on a live vehicle without a hardware kill switch. Authentication on the HTTP endpoint is on the roadmap.

From the GitHub API

Repository facts

Repository facts for pan-robotics/bus-mcp, from the GitHub API
Repositorypan-robotics/bus-mcp
Stars2
LicenseMIT Permissive
LanguagePython
Last push30 Jun 2026 3 mo ago

Tags

Report a problem with this entry