From 9810d356378412c9a9e7e9a0527d53c313a760dc Mon Sep 17 00:00:00 2001 From: Ryan Malloy Date: Fri, 30 Jan 2026 21:38:14 -0700 Subject: [PATCH] Remove esp_binary_optimize tool No real esptool operation backs "optimize firmware binary". Size optimization happens at compile-time via ESP-IDF menuconfig, not as a post-processing step on a .bin file. The analysis use case is already covered by esp_firmware_analyze. --- src/mcp_esptool_server/components/firmware_builder.py | 7 ------- src/mcp_esptool_server/server.py | 2 +- 2 files changed, 1 insertion(+), 8 deletions(-) diff --git a/src/mcp_esptool_server/components/firmware_builder.py b/src/mcp_esptool_server/components/firmware_builder.py index 5ae0a6c..ee0a13e 100644 --- a/src/mcp_esptool_server/components/firmware_builder.py +++ b/src/mcp_esptool_server/components/firmware_builder.py @@ -38,13 +38,6 @@ class FirmwareBuilder: """Analyze firmware binary structure""" return {"success": True, "note": "Implementation coming soon"} - @self.app.tool("esp_binary_optimize") - async def optimize_binary( - context: Context, input_path: str, output_path: str - ) -> dict[str, Any]: - """Optimize firmware binary for size/performance""" - return {"success": True, "note": "Implementation coming soon"} - async def health_check(self) -> dict[str, Any]: """Component health check""" return {"status": "healthy", "note": "Firmware builder ready"} diff --git a/src/mcp_esptool_server/server.py b/src/mcp_esptool_server/server.py index a664f39..1ca2499 100644 --- a/src/mcp_esptool_server/server.py +++ b/src/mcp_esptool_server/server.py @@ -169,7 +169,7 @@ class ESPToolServer: "esp_efuse_read", "esp_efuse_burn", ], - "firmware": ["esp_elf_to_binary", "esp_firmware_analyze", "esp_binary_optimize"], + "firmware": ["esp_elf_to_binary", "esp_firmware_analyze"], "ota": ["esp_ota_package_create", "esp_ota_deploy", "esp_ota_rollback"], "production": ["esp_factory_program", "esp_batch_program", "esp_quality_control"], "diagnostics": [