PlatformIO
PYPI · PLATFORMIO.MCP · SCANNED SEP 22
PlatformIO for AI agents: build, flash, serial monitor, tests, crash decoding, size reports.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security43
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs a script at install time (build_backend) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- 2 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2644 tokens (~91/item across 29 items; 29 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pio_clean" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the PlatformIO MCP server?
PlatformIO runs locally as a PyPI package, launched with uvx platformio.mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · platformio.mcp
claude mcp add powerdragonfire-platformio-mcp -- uvx platformio.mcp
{
"mcpServers": {
"powerdragonfire-platformio-mcp": {
"command": "uvx",
"args": [
"platformio.mcp"
]
}
}
} {
"servers": {
"powerdragonfire-platformio-mcp": {
"command": "uvx",
"args": [
"platformio.mcp"
]
}
}
} codex mcp add powerdragonfire-platformio-mcp -- uvx platformio.mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"powerdragonfire-platformio-mcp": {
"type": "local",
"command": [
"uvx",
"platformio.mcp"
],
"enabled": true
}
}
} openclaw mcp add powerdragonfire-platformio-mcp --command uvx --arg platformio.mcp
mcp_servers:
powerdragonfire-platformio-mcp:
command: "uvx"
args: ["platformio.mcp"] {
"McpServers": {
"powerdragonfire-platformio-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"platformio.mcp"
]
}
}
} assistant mcp add powerdragonfire-platformio-mcp -t stdio -c uvx -a platformio.mcp
{
"mcpServers": {
"powerdragonfire-platformio-mcp": {
"command": "uvx",
"args": [
"platformio.mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed pypi/platformio.mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | unreviewed | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pio_board_info ~55
Full details for one board id: MCU, clock, RAM and flash sizes in bytes, supported frameworks, connectivity, and debug probes. Use it to learn memory limits before writing code.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_build ~96
Compile the project (`pio run`). Returns a status, parsed compiler errors and warnings with file/line/column, RAM and Flash usage percentages, the last 40 lines of output, and a path to the full log. Fix the listed errors, then build again. First builds may take minutes while toolchains download.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| jobs | – | – | – |
| project_dir | – | – | – |
| verbose | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_check ~97
Static analysis (`pio check`, cppcheck by default; clangtidy/pvs-studio if configured). Returns defects grouped and sorted by severity with file, line, CWE, and message. severity is the minimum level to report (low|medium|high).
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| pattern | – | – | – |
| project_dir | – | – | – |
| severity | string | – | – |
| skip_packages | boolean | – | – |
| tool | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_clean ~51
Delete build artifacts for an env (`pio run -t clean`); full=true also removes downloaded dependencies (fullclean).
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| full | boolean | – | – |
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_decode_backtrace ~167
Turn a crash dump into source locations. Give `text` containing an ESP32/ESP-IDF 'Guru Meditation' register dump and 'Backtrace: 0x...:0x...' line, or a Cortex-M HardFault pc/lr dump, or give `session_id` of an open monitor session to scan its buffer. Resolves every program-counter address with the toolchain's addr2line against the env's firmware.elf and returns function, file, line (with inlined frames) per address, plus the crash cause and reset reason. The ELF must be from the same build that was flashed.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| include_all_hex | boolean | – | – |
| project_dir | – | – | – |
| session_id | – | – | – |
| text | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_flash_and_verify ~208
Hardware-in-the-loop check with no human: build + flash (`pio run -t upload`), then open the serial port and watch the boot log until `expect` (regex) matches -> verdict pass, or `fail_on` matches -> verdict fail with the crash automatically decoded to file:line, or timeout_s elapses -> verdict timeout. Port and baud come from platformio.ini (monitor_port/monitor_speed) or the single detected board. Set expect to a line your firmware prints once it is healthy, e.g. 'WiFi connected'. Blocked under build_only/read_only policy.
| Name | Type | Req | Description |
|---|---|---|---|
| baud | – | – | – |
| env | – | – | – |
| expect | string | – | – |
| fail_on | string | – | – |
| max_lines | integer | – | – |
| monitor_port | – | – | – |
| project_dir | – | – | – |
| settle_s | number | – | – |
| stop_open_sessions | boolean | – | – |
| timeout_s | number | – | – |
| upload_port | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_list_boards ~112
Search PlatformIO's board catalogue (~1,700 boards). Query matches board id, name, MCU, or vendor, e.g. 'esp32-s3', 'uno', 'STM32F4', 'DOIT'. Returns board ids plus MCU, clock, RAM, flash, and frameworks. Use the returned `id` in platformio.ini or pio_project_init.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | – | – | – |
| limit | integer | – | – |
| platform | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_list_devices ~64
List serial ports (`pio device list`) and flag which ones look like USB dev boards (CP210x, CH340, FTDI, ESP, Arduino, ST-Link...). Use the port with pio_upload, pio_monitor_start, or pio_monitor_capture.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pio_list_targets ~48
List extra build targets the platform offers for this project, such as buildfs, uploadfs, erase, size, or menuconfig.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_monitor_capture ~103
One-shot serial capture with no session to manage: open the port, collect output for up to `seconds` (or until regex `until` matches), close the port, and return the lines. Ideal right after pio_upload to grab the boot log.
| Name | Type | Req | Description |
|---|---|---|---|
| baud | – | – | – |
| env | – | – | – |
| max_lines | integer | – | – |
| port | – | – | – |
| project_dir | – | – | – |
| seconds | number | – | – |
| until | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_monitor_list ~28
List open serial monitor sessions with port, baud, buffered line count, and next cursor.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pio_monitor_read ~119
Read new serial lines from a session since `cursor` (start at 0) and get the next cursor back. Set wait_for to a regex to block up to timeout_s until a matching line arrives (e.g. wait_for='setup done|Guru Meditation'). Without wait_for and with timeout_s>0 it waits for at least one new line.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | – |
| max_lines | integer | – | – |
| session_id | string | yes | – |
| timeout_s | number | – | – |
| wait_for | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_monitor_start ~115
Open a background serial monitor session and return a session_id. Port and baud default from platformio.ini (monitor_port/monitor_speed) when project_dir is given, else the single detected dev board and 115200. Output is buffered (ring buffer, max_lines); read it with pio_monitor_read. The session holds the port, so stop it before pio_upload.
| Name | Type | Req | Description |
|---|---|---|---|
| baud | – | – | – |
| env | – | – | – |
| max_lines | integer | – | – |
| port | – | – | – |
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_monitor_stop ~28
Close a serial monitor session and release the port.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_monitor_write ~59
Send text to the device over the open session's serial port (newline appended by default). Blocked under build_only/read_only policy.
| Name | Type | Req | Description |
|---|---|---|---|
| newline | boolean | – | – |
| session_id | string | yes | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_pkg_install ~101
Install a library/platform/tool into the project and add it to platformio.ini (`pio pkg install -l spec`). spec examples: 'bblanchon/ArduinoJson@^7', 'adafruit/Adafruit NeoPixel', 'https://github.com/user/repo.git'. Restrict to one env with env=.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
| spec | string | yes | – |
| type | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_pkg_list ~37
List resolved platform, toolchain, and library packages for the project with versions.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_pkg_outdated ~31
Show which project dependencies have newer versions available.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_pkg_search ~73
Search the PlatformIO registry for libraries (default), platforms, or tools. Returns owner/name specs with the latest version and description. Example query: 'ArduinoJson', 'ssd1306 display', 'mqtt'.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| query | string | yes | – |
| type | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_pkg_uninstall ~49
Remove a library/platform/tool from the project and platformio.ini.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
| spec | string | yes | – |
| type | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_pkg_update ~33
Update dependencies within the version ranges declared in platformio.ini.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_project_envs ~60
Read platformio.ini and list every environment with its board, platform, framework, monitor/upload settings, lib_deps, and build_flags, plus which envs are default. Cheap; call before building or flashing.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_project_init ~137
Create a new PlatformIO project (or add an environment to an existing one) with `pio project init`. Give an absolute project_dir, a board id from pio_list_boards, and optionally a framework (arduino, espidf, stm32cube, zephyr, ...). project_options are extra platformio.ini keys like 'monitor_speed=115200' or 'lib_deps=bblanchon/ArduinoJson'. Never hand-write platformio.ini for a new project; use this.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | – |
| framework | – | – | – |
| project_dir | string | yes | – |
| project_options | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_project_metadata ~60
Computed build metadata per environment: defines, include paths, compiler paths and flags, library dirs. Useful for understanding what the compiler actually sees. Triggers platform/toolchain install on first use.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_run_target ~74
Run one named target from pio_list_targets (e.g. 'buildfs', 'uploadfs', 'erase', 'size'). Flash-related targets follow the same policy rules as pio_upload.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
| target | string | yes | – |
| upload_port | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_size_report ~130
Explain where flash and RAM go in the built firmware.elf: text/data/bss totals with percent of the board's flash and RAM, loaded sections classified as flash/ram, the biggest symbols (demangled, with file:line), and per-source-file totals. Use it to shrink firmware on purpose: drop the largest fonts/tables, remove unused features, tune build flags. Run pio_build first; `filter` is a regex applied to symbol names and file paths.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| filter | – | – | – |
| project_dir | – | – | – |
| top | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_system_info ~69
Check that PlatformIO is installed and report its version, core directory, the active safety policy (full | build_only | read_only), the log directory, and any open serial monitor sessions. Call this first in a session; if PlatformIO is missing the result tells you how to install it.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pio_test ~140
Run PlatformIO unit tests (`pio test`, Unity framework) and return per-case pass/fail with file, line, and message. Tests live in test/test_<name>/. Native envs run on the host; embedded envs build, flash, and read results over serial (set without_uploading=true to only build them). filter/ignore take glob patterns like 'test_math*'.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| filter | – | – | – |
| ignore | – | – | – |
| project_dir | – | – | – |
| upload_port | – | – | – |
| verbose | boolean | – | – |
| without_building | boolean | – | – |
| without_uploading | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pio_upload ~80
Build and flash firmware to the connected board (`pio run -t upload`). Refuses while a serial monitor session holds the port; stop it first. Pass upload_port when several boards are attached. Blocked when PLATFORMIO_MCP_POLICY is build_only or read_only.
| Name | Type | Req | Description |
|---|---|---|---|
| env | – | – | – |
| project_dir | – | – | – |
| upload_port | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the PlatformIO MCP server?
PlatformIO is an MCP server listed in the public MCP registry as io.github.powerdragonfire/platformio.mcp. PlatformIO for AI agents: build, flash, serial monitor, tests, crash decoding, size reports. This page covers its PyPI package (platformio.mcp).
Is the PlatformIO MCP server safe to use?
PlatformIO scores 47 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PlatformIO MCP server expose?
PlatformIO exposes 29 tools: pio_system_info, pio_list_boards, pio_board_info, pio_project_init, pio_project_envs, and 24 more. Their descriptions and schemas cost roughly 2,424 tokens of context every time the server is loaded.
Is the PlatformIO MCP server still maintained?
PlatformIO is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.