A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
158 โ ยท horw/esp-mcp ยท read from the repository page ยท (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list ยท type: MCP server
Harvest history
first seen 2026-10-09 ยท last seen 2026-10-16 ยท seen 32ร ยท listed by 10 sources
Score
score 1,003 ยท 158 โ ยท 10 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository horw/esp-mcp๏ผfirst catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
The goal of this MCP is to: - Consolidate ESP-IDF and related project commands in one place. - Simplify getting started using only LLM communication. How to contribute to the project Simply find a command that is missing from this MCP and create a PR for it! If you want someone to help you with this implementation, just open an issue. Notice This project is currently a **Proof of Concept (PoC)** for an MCP server tailored for ESP-IDF workflows. **Current Capabilities:** **Core Features:** * run_esp_idf_install: Install ESP-IDF dependencies and toolchain via install.sh. * create_esp_project: Create a new ESP-IDF project. * setup_project_esp_target: Set target chip for ESP-IDF projects (esp32, esp32c3, esp32s3, etc.). * build_esp_project: Build ESP-IDF projects with incremental build support. * list_esp_serial_ports: List available serial ports for ESP devices. * flash_esp_project: Flash built firmware to connected ESP devices. * run_pytest: Run pytest tests with pytest-embedded support for ESP-IDF projects. **Additional Features:** * Flexible ESP-IDF path management: supports per-project ESP-IDF versions via idf_path parameter. * SDK config management: supports custom sdkconfig_defaults files for build configuration (multiple files can be specified separated by semicolons). * Build time tracking for performance monitoring. * Optional port specification for flashing operations. * Includes experimental support for automatic issue fixing based on build logs. **Vision & Future Work:** The long-term vision is to expand this MCP into a comprehensive toolkit for interacting with embedded devices, potentially integrating with home assistant platforms, and streamlining documentation access for ESP-IDF and related technologies. We envision features such as: * Broader ESP-IDF command support (e.g., monitor, menuconfig interaction if feasible). * Device management and information retrieval. * Integration with other embedded development tools and platforms. Your ideas and contributions are welcome! Please feel free to discuss them by opening an issue. Install First, clone this MCP repository: Then, configure it in your chatbot. The JSON snippet below is an example of how you might configure this esp-mcp server within a chatbot or an agent system that supports the Model Context Protocol (MCP). The exact configuration steps and format may vary depending on the specific chatbot system you are using. Refer to your chatbot's documentation for details on how to integrate MCP servers. A few notes on the configuration: * **command**: This should be the full path to your uv executable if you are using it, or your Python interpreter (e.g., /usr/bin/python3 or C:\\Python39\\python.exe) if you plan to run main.py directly. * **args**: * The first argument to --directory should be the absolute path to where you cloned the esp-mcp repository. * If you're using uv, the arguments run main.py are appropriate. If you're using Python directly, you might only need main.py in the args list, and ensure your command points to the Python executable.