mpftp
MicroPython and CircuitPython board tools for VS Code and compatible derivatives
mpftp brings microcontroller board management directly into your modern code editor (VS Code, Google Antigravity IDE, Cursor, VSCodium):
- An In-Editor Alternative to Thonny: Edit board files, transfer files, install packages (
mip/circup), and flash firmware without switching back and forth to external IDEs or standalone tools. - Embedded Serial REPL: The interactive REPL opens directly inside your editor's Terminal panel, allowing you to test and inspect code live alongside your editor tabs and AI coding agents.
- Wi-Fi Fast MIP Transfers: Transferring
wifi.pyand creatingsecrets.pyon Wi-Fi enabled boards enables on-boardmippackage installation directly over the network, which is significantly faster than serial file transfers. - Visual Firmware Builder: A GUI companion for firmware workspaces (such as cmods), allowing you to download official releases or build and flash custom firmware from the UI.
- Completely Optional: If you are already comfortable with command-line tools (
mpremote,esptool,circup) or standalone IDEs, you can continue using them.mpftpis provided as an all-in-one in-editor workbench.
Published as pydevices.mpftp under PyDevices.
Documentation
- User guide — getting started, File Transfer, REPL, Firmware workspace, autosize, troubleshooting
- Aggregator & user modules — workspace
micropython.cmake/manifest-micropython.pycontract - Developers guide — architecture, discovery contract, packaging, contribution
- Agent guide — agent/CLI workflows: board ops, flash recovery, pointers to aggregator docs
Features
- Dual-Pane File Transfer: Local ↔ board file management (upload, download, mkdir, new file, delete, rename, drag-and-drop)
- Live In-Editor Editing: Open and edit files directly on the board with automatic save-back and optional SHA-256 verification
- Integrated Terminal REPL: Hardware serial REPL embedded right in the editor Terminal workspace
- Automatic Interpreter Detection: Connects over serial, automatically identifies MicroPython or CircuitPython, and synchronizes the RTC
- Package Installation: Install packages with
mip(MicroPython) orcircup(CircuitPython) - Visual Firmware Workbench: Detect board hardware, download official MicroPython builds, or build and flash custom firmware workspaces (ESP32, RP2040, SAMD)
- AI Agent-Friendly: Local TCP RPC and agent CLI interface sharing the active editor session
Requirements
- VS Code or compatible derivative (such as Google Antigravity IDE, Cursor, VSCodium) (engine
^1.85.0) - Python 3 with
mpremote- WSL / Windows serial: Windows Python +
pip install mpremote - Native Linux: venv or
mpftp.pythonPath
- WSL / Windows serial: Windows Python +
- For CircuitPython packages:
circupon the same Python (pip install circup)
Install
Marketplace: search for mpftp by pydevices, or install a .vsix:
npm install
npm run package
# Extensions: Install from VSIX… → mpftp-*.vsix
Development (Cursor Remote-WSL):
npm install && npm run compile
./scripts/install-cursor-wsl.sh
# Developer: Reload Window
Quick start
- mpftp: Connect to Board — pick a port
- Open File Transfer — move files; open REPL for the shell
- Install Package — mip (MicroPython) or circup (CircuitPython) by detected interpreter
- Firmware — Detect a board, then Download an official MicroPython image or Build from a firmware workspace
A firmware workspace is a folder that contains micropython/ (or is the MicroPython tree). Port SDKs go in that workspace as directories/symlinks, or via environment variables — see the user guide.
Commands (selection)
| Command | Action |
|---|---|
mpftp: Connect to Board |
Port picker; interrupt + interpreter-aware clean |
mpftp: Resume Last Device |
Reconnect previous port |
mpftp: Open File Transfer in Panel / Editor |
Dual-pane UI |
mpftp: Open REPL |
ANSI terminal |
mpftp: Build & Flash Firmware… |
MicroPython firmware panel |
mpftp: Interrupt / Soft Reset / Hard Reset |
Board control |
mpftp: Install Package |
mip or circup by interpreter |
Settings (selection)
| Setting | Purpose |
|---|---|
mpftp.workspacePath |
Firmware workspace (MicroPython + optional SDK trees) |
mpftp.pythonPath |
Sidecar Python (empty on WSL → Windows python.exe) |
mpftp.buildPythonPath |
Native Python for builds |
mpftp.verifyTransfers |
SHA-256 after file transfer |
mpftp.autoReconnectAfterReset |
Reconnect after hard reset |
Full list: VS Code Settings → search mpftp, or user guide.
License
MIT — see LICENSE if present in the package, otherwise the repository license file.
Metadata
Release files for pydevices-mpftp 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pydevices_mpftp-0.0.3.tar.gz | 83.7 kB | Without provenance | Details for pydevices_mpftp-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pydevices_mpftp-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for pydevices_mpftp-0.0.3-py3-none-any.whl |
Total release size: 168.4 kB
Release files / pydevices_mpftp-0.0.3.tar.gz
| Download URL | pydevices_mpftp-0.0.3.tar.gz |
|---|---|
| Size | 83.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05fde7303f3815a0b20f25bf48f7de060f4682d1c793a7e96498ee587d0b7d39
|
|
BLAKE2b-256 checksum How to use checksums |
ff54e975484dc70f977ab1b2c17a5d83def38957d3efb8bff07b3faa63205cab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / pydevices_mpftp-0.0.3-py3-none-any.whl
| Download URL | pydevices_mpftp-0.0.3-py3-none-any.whl |
|---|---|
| Size | 84.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0fe5557c95dd3e3f06a1c28e3077c8d093a5372a4ab2e929bfcb7968106f3585
|
|
BLAKE2b-256 checksum How to use checksums |
924c4e1ebfbdfbeaf2255512b31194b41ed2b319b126ab4862c05e64cf92f15d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for pydevices-mpftp 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.