Skip to content
ESP-IDF Tools MCP Server

ESP-IDF Tools MCP Server

by Espressif Systems
Released
Docs
Developer Tools

Summary

Espressif's local MCP server built into idf.py — lets an AI client set the chip target, build, flash and clean an ESP-IDF project and read back config, build status and connected serial ports.

Features

  • Built into idf.py — no separate server to install
  • Set chip target, build, flash and clean an ESP-IDF project
  • Reads project config, build status and connected serial ports
  • Runs locally over stdio, keeping hardware and toolchain on your machine
  • Requires ESP-IDF v6.0+ and EIM v0.8.1+

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "ESP-IDF Tools MCP Server" tools will be available.
{
  "mcpServers": {
    "esp-idf-tools-mcp": {
      "command": "eim",
      "args": [
        "run",
        "idf.py mcp-server"
      ],
      "env": {
        "IDF_MCP_WORKSPACE_FOLDER": "${workspaceFolder}"
      }
    }
  }
}

Description

ESP-IDF Tools MCP Server is Espressif's own Model Context Protocol integration for ESP32 firmware work. It is not a separate download: the server is built into idf.py, the ESP-IDF build tool, and started with idf.py mcp-server.

Embedded development has an awkward gap for coding agents. An agent can write firmware perfectly well, but it cannot tell whether the code compiles for the right target, whether the board is even plugged in, or which serial port it appeared on. This server closes that loop by exposing the build system and the attached hardware as MCP tools and resources.

Tools

  • set_target(target) — select the chip target
  • build_project() — compile the project
  • flash_project(port) — flash firmware to a connected device
  • clean_project() — remove build artifacts

Resources

  • project://config — the project's configuration
  • project://status — build status and produced artifacts
  • project://devices — serial ports currently connected

Requirements

ESP-IDF v6.0 or later with the mcp feature enabled, plus ESP-IDF Installation Manager (EIM) v0.8.1 or later. The server runs locally over stdio, so the board, the toolchain and the agent all stay on the developer's own machine.

Related MCP Servers

MCP: tinymcp

by Golioth

Golioth's experimental MCP server that lets an LLM drive real embedded devices — device RPCs become MCP tools, with schemas stored in LightDB State and calls routed through the Golioth cloud.

Developer Tools

MCP: Memfault MCP Server

by Memfault (Nordic Semiconductor)

Remote MCP server for Memfault (Nordic Semiconductor) exposing 18 read-only tools over device fleet telemetry — device vitals, timeseries, crash issues, traces, metrics and software versions.

Cloud & Infrastructure

MCP: Daytona MCP Server

by Daytona

Daytona's official MCP server: give an agent a disposable cloud sandbox with a file system, git, process execution, computer use and a live preview URL.

Developer Tools

MCP: Git

by Model Context Protocol

Read, search, and manipulate Git repositories — status, diffs, logs, branches, commits, and more.

CLIDevelopers
Browse all MCP servers →