Picodev Lab

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.PICODEV-SAS/picodev-lab and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 21 Oct 2026. Not supplied by the maker.

• list_setups

  The available setups, their modes (free, challenge) and their benches.

• open_session

  Create a session (mode: free or challenge). Give open_url to the human: nothing simulates until they open it in their browser.

• push_to_editor

  Replace the code in the human's browser and, if run, compile it in the lab's cloud and start it. The fallback of push_program: use it only when the toolchain to compile locally is missing (no ardu

• push_program

  Send a program compiled on the visitor's machine (Intel HEX text, 48 KiB at most, e.g. arduino-cli's <sketch>.ino.hex) to the human's browser, which loads it in the simulator without compiling and

• read_simulation

  Last state (with circuit, the browser's components and wires), last compilation and the events after since_ms (2000 at most). In challenge mode: the level's brief and its results. circuit_modified

• set_visibility

  Change the visibility (private, link, public). Returns the viewer link; current viewers are disconnected.

• queue_join

  Take a place in the queue for benches of this kind (for example real or sim). The browser must be connected.

• queue_status

  The session's place: state none, waiting (position, estimated wait eta_s) or turn (bench, end of the turn ends_at, Unix seconds).

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.