esp32-workbench-mqtt

Start, stop, and check status of a mosquitto MQTT broker on the ESP32 workbench.

161|53|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/SensorsIot/Universal-ESP32-Workbench --skill esp32-workbench-mqtt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: esp32-workbench-mqtt
Source: https://github.com/SensorsIot/Universal-ESP32-Workbench/tree/main/.claude/skills/esp32-workbench-mqtt
Command: npx skills add https://github.com/SensorsIot/Universal-ESP32-Workbench --skill esp32-workbench-mqtt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ESP32 development often requires a local MQTT broker for testing. This Skill provides a ready-to-use broker on the Universal ESP32 Workbench to simplify device testing.

Core Features & Use Cases

  • Start, stop, and check status of a mosquitto broker deployed on the workbench.
  • Enable ESP32 devices to publish and subscribe over the workbench's WiFi AP for isolated testing.
  • Use in CI-like scenarios to validate MQTT-based firmware flows and provisioning.

Quick Start

Start the broker using the API and connect ESP32 devices to the workbench WiFi to begin MQTT testing.

Frequently Asked Questions about esp32-workbench-mqtt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test ESP32 MQTT clients with a local broker?

To test ESP32 MQTT clients, you can start a local mosquitto broker on the Universal ESP32 Workbench via HTTP endpoints, allowing devices to publish and subscribe over the workbench WiFi AP for isolated development and QA.

How do I start and stop the mosquitto broker on the ESP32 workbench?

You start and stop the mosquitto broker by sending HTTP POST requests to the /api/mqtt/start and /api/mqtt/stop endpoints, with GET /api/mqtt/status available to check the current broker state.

Do I need mosquitto installed locally to use MQTT testing on the ESP32 workbench?

Yes, this Skill requires mosquitto to be installed on the workbench to provide the ready-to-use MQTT broker environment for testing ESP32 MQTT clients.

What IP address should ESP32 devices use to connect to the MQTT broker on the workbench?

ESP32 devices should connect to the MQTT broker at the IP address 192.168.4.1 on port 1883 when they are connected to the workbench WiFi AP.

Can I use the ESP32 workbench MQTT broker for CI-like firmware validation?

Yes, you can use this MQTT broker setup in CI-like scenarios to validate MQTT-based firmware flows and provisioning by simulating a testing environment over the WiFi AP.