esp-idf-monitor-mcp MCP Server
jinw06k/esp-idf-monitor-mcp
Drop-in replacement for esp-idf/tools/idf_py_actions/mcp_ext.py that adds IDF monitor support to idf.py mcp-server.
claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
jinw06k/esp-idf-monitor-mcp is a Python MCP server licensed under Apache-2.0. Drop-in replacement for esp-idf/tools/idf_py_actions/mcp_ext.py that adds IDF monitor support to idf.py mcp-server.
Ranked #33 out of 124 indexed tools.
Actively maintained with commits in the last week.
Ecosystem
Score Breakdown
3 stars → early stage
Last commit today → actively maintained
No issues filed → no history to score
1 contributor → solo project
No dependents → no downstream usage
Weights: Freshness 25% · Issue Health 25% · Dependents 25% · Stars 15% · Contributors 10% · How we score →
How to Improve
Matched Queries
From the README
# esp-idf-mcp-monitor Serial monitor tools for the ESP-IDF MCP server. Drop-in replacement for `tools/idf_py_actions/mcp_ext.py` that adds interactive monitor support to `idf.py mcp-server`. **Upstream PR:** [espressif/esp-idf#18385](https://github.com/espressif/esp-idf/pull/18385) ## The Problem ESP-IDF v6.0 introduced an MCP server (`idf.py mcp-server`) with tools for `build`, `flash`, `set-target`, and `clean`. But there's no way for an AI agent to read serial output from the device — no boot logs, no error messages, no runtime diagnostics. The agent can push firmware to the board but can't see what happens next. Two technical barriers prevent simply wrapping `idf.py monitor`: 1. **TTY requirement** — `idf_monitor.py` checks `sys.stdin.isatty()` and refuses to start without a real terminal 2. **Process tree cleanup** — `idf.py` spawns `idf_monitor.py` as a child; killing only the parent leaves the child holding the serial port open ## What This Adds Five new MCP tools, allRead full README on GitHub →
Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.