사이트맵 Agent는 PlatformIO MCP 런타임에 내장된 임베디드 개발을 위한 오픈 소스, Agent-First 하드웨어 실행 레이어입니다.

릴리스 상태

canonical 3.1.0 실행 시간은 간행됩니다. 3.2.0 후보자는 pio-agent CLI 기본 어댑터 (요청하지 않는 한 유지), 기본 Codex 패널과 공개 플러그인 목록 메타데이터를 추가합니다. 이름 * changelog, 호환성 가이드, and Distribution readiness for 구현 행동과 각 패키지 이름의 발행 상태.

상표와 겸용성

PIO Agent는 제품 및 Codex 플러그인 이름입니다. **PlatformIO MCP **는 MCP 런타임과 기존 설치에 사용되는 호환성 정체성입니다. Codex 플러그인 ID, 마켓 플레이스 ID, 구성 키 및 기술 네임스페이스는 platformio-mcp 남아 있습니다. npm에서 platformio-mcp은 canonical 패키지이지만 pio-mcp]과 pio-agent]는 delegate가 얇은 호환성 패키지입니다. canonical 패키지는 platformio-mcp과 pio-agent] 실행 가능한 이름을 모두 설치합니다. 새로운 사용자는 인터페이스를 통해 PIO Agent를 볼 때 기존의 소비자 업그레이드를 할 수 있습니다.

PIO Agent

PIO Agent is the open-source, agent-first hardware execution layer for embedded development, built on the PlatformIO MCP runtime.

Release status

The canonical 3.1.0 runtime is published. The 3.2.0 candidate makes the pio-agent CLI the primary adapter (nothing stays running unless asked), and adds a native Codex panel and public plugin listing metadata. See the changelog, compatibility guide, and distribution readiness for implemented behavior and the publication status of each package name.

Brand and Compatibility

PIO Agent is the product and Codex Plugin name. PlatformIO MCP is the underlying MCP runtime and the compatibility identity used by existing installations. The Codex plugin ID, marketplace ID, configuration keys, and skill namespace remain platformio-mcp. On npm, platformio-mcp is the canonical package while pio-mcp and pio-agent are thin compatibility packages that delegate to it. The canonical package also installs both platformio-mcp and pio-agent executable names. This lets existing consumers upgrade without migration while new users see PIO Agent throughout the interface.

It exposes PlatformIO workflows for board discovery, project setup, build, flash, monitor, diagnostics, and task orchestration through:

• an MCP server adapter
• a first-class CLI adapter (platformio-mcp / pio-agent)
• an optional local dashboard for visibility and control

MCP is one adapter. PlatformIO is the first backend.

Quick start (recommended)

npm install -g platformio-mcp
pio-agent devices
pio-agent build --project-dir . --json

No server, no client configuration, nothing left running between commands.

Using it with a coding agent

Install the skills and point your agent at the pio-agent binary. The pio-manager skill documents every command.

MCP server (optional)

MCP remains fully supported for clients that prefer it:

claude mcp add platformio -- node /path/to/platformio-mcp/build/index.js

Note that each session that connects this way runs its own server process. The CLI above avoids that. See Manual MCP Config below for other hosts.

Agent-First Capabilities

• Project readiness validation (agent_validate_project)
• Rich build diagnostics with structured error taxonomy (agent_build_diagnose)
• Board-aware GPIO safety audits (agent_safe_pin_audit)
• Flash + monitor + runtime assertions (agent_flash_monitor_verify)
• Persistent workflow artifacts in .pio-mcp-workspace/ (lastAgentReport.json, boardReport.json)
• Board intelligence reports (agent_generate_board_report)
• Policy profile introspection (get_policy_status)
• Exact project/environment/device bindings (agent_resolve_target)