Loading...
{
"mcpServers": {
"esp-run": { // "esp-run" is an arbitrary name you can assign to this server configuration.
"command": "<path_to_uv_or_python_executable>",
"args": [
"--directory",
"<path_to_cloned_esp-mcp_repository>", // e.g., /path/to/your/cloned/esp-mcp
"run",
"main.py" // If using python directly, this might be just "main.py" and `command` would be your python interpreter
],
"env": {
"IDF_PATH": "<path_to_your_esp-idf_directory>" // e.g., ~/esp/esp-idf or C:\\Espressif\\frameworks\\esp-idf
}
}
}
}run_esp_idf_installInstalls ESP-IDF dependencies and toolchain.
Modifies the system environment by installing dependencies.
create_esp_projectCreates a new ESP-IDF project.
Creates files and directories on the file system.
setup_project_esp_targetSets the target chip for an ESP-IDF project.
Modifies project configuration files.
build_esp_projectBuilds an ESP-IDF project.
Executes build scripts that could potentially contain malicious code.
list_esp_serial_portsLists available serial ports for ESP devices.
Read-only operation that does not modify the system.
flash_esp_projectFlashes built firmware to a connected ESP device.
Writes firmware to a device, potentially causing irreversible changes.
run_pytestRuns pytest tests for an ESP-IDF project.
Executes tests that could potentially interact with the system.
This MCP offers convenience for ESP-IDF development, but it's crucial to validate project paths and configurations to prevent unintended firmware flashing or build errors. While it doesn't provide arbitrary shell access, the potential for flashing incorrect firmware warrants careful usage.