A simple HTTP server library for building web interfaces and APIs on MicroPython-powered devices like ESP8266/ESP32.
MicroPyServer is a lightweight HTTP server library for MicroPython, enabling developers to run web servers on microcontrollers like ESP8266 and ESP32. It allows these devices to handle HTTP requests, serve web pages, and create simple APIs, turning them into web-accessible IoT endpoints. The library solves the problem of adding web connectivity to resource-constrained embedded projects without complex setup.
Embedded developers and hobbyists working with MicroPython on ESP8266/ESP32 boards who need to add web server capabilities for remote control, monitoring, or simple web interfaces.
Developers choose MicroPyServer for its simplicity and direct integration with MicroPython's hardware APIs, offering essential web server features without the overhead of larger frameworks. It's specifically optimized for microcontroller environments where memory and processing power are limited.
MicroPyServer is a simple HTTP server for MicroPython projects.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Designed specifically for MicroPython on ESP boards, it keeps memory footprint low, allowing web servers on devices with as little as 4MB of RAM.
Seamlessly works with MicroPython's machine module, enabling direct GPIO control via HTTP requests, as shown in the LED control example.
Simple add_route method supports custom paths and HTTP methods, making it easy to define API endpoints or web pages.
Includes utilities like get_request_query_params() to easily extract query parameters and POST data from HTTP requests.
The README explicitly warns that version 1.1.x is incompatible with older versions, causing maintenance headaches for existing projects.
Requires downloading and unpacking code manually, with no support for pip or other package managers, complicating deployment.
Limited to basic examples and a method list, lacking detailed tutorials, API references, or best practices guidance.
Lacks built-in support for HTTPS, WebSockets, static file serving, or template engines, requiring custom implementation for common needs.