ModelsAtlas
Explore
Atlas / MCP servers / horw / Esp

EspSAFE

mcp/horw/esp
MCP server by horw · esp idf · esp32 · mcp · Audited 2026-10-07
⚑ Report / re-scanSource ↗

Centralize ESP32 related commands and simplify getting started with seamless, LLM-driven interaction and help.

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
7 4r · 3w · 0d
Transport
stdio
License
—
Stars
158
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://mseep.ai/app/horw-esp-mcp)

Goal

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 sup
Read from source at commit ad73445c63acOBSERVED · 2026-10-07
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add esp-mcp -- uvx esp-mcp
claude-desktop
{
  "mcpServers": {
    "esp-mcp": {
      "command": "uvx",
      "args": [
        "esp-mcp"
      ]
    }
  }
}
03

Exposed tools (7)

4 read · 3 write · 0 destructive.

ToolRiskDescription
build_esp_projectreadBuild an ESP-IDF project. Can Incremental Build. Similar to `idf.py build`.
create_esp_projectwrite
flash_esp_projectreadFlash built firmware to a connected ESP device.
list_esp_serial_portsreadList available serial ports for ESP devices.
run_esp_idf_installwriteRun the install.sh script in the ESP-IDF directory to install ESP-IDF dependencies and toolchain.
run_pytestwriteRun pytest tests in a project. Supports pytest-embedded for ESP-IDF/ESP32 testing.
setup_project_esp_targetread
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (2)

LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence
INFOInventory / provenance · inv.oversize · CWE-1104
result.gif
result.gif
Why it matters. 12143217 bytes not read

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-07 · audit v0.4.1 · source sha ad73445c63acfull audit observations/trust-audit/mcp-server/horw__esp.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-07ad73445c63acSAFEB89first audit
06

Questions

What is the Esp MCP server?

Centralize ESP32 related commands and simplify getting started with seamless, LLM-driven interaction and help.

What tools does Esp expose?

7 in total: 4 read-only, 3 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Esp safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Esp need?

No credential environment variables were found in its source, so it appears to need none.

How does Esp run?

It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as esp-mcp.

How current is this page?

The grade is for one exact copy of the source (ad73445c63ac), read on 2026-10-07. The repository is watched and re-audited when it changes.

Advertisement