Official MCP server for esa.io - a documentation sharing service for teams
Picodev Lab is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Arduino benches simulated in the browser: sessions, sketch push, simulation, tests, challenges.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http picodev-lab-mcp https://lab.picodev.fr/mcp
# 2 — ask your agent for something these tools do
# decode_capture, list_setups, open_session and 20 more
Picodev Lab costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http picodev-lab-mcp https://lab.picodev.fr/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Decode a ready logic capture of the session (browser or bench). protocol "uart" with channels {rx} and options {baud (300-1000000, 9600), bits (5-9, 8), parity (none, even, odd), stop (1, 2), invert (false)}; "spi" with {sck, mosi?, miso?, cs?} (one data pin at least) and options {mode (0-3, 0), bit_order (msb, lsb), bits (8)}; "i2c" with {scl, sda}. channels are pins of the capture. R
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| capture | string | yes | — |
| protocol | string | yes | — |
| channels | object | yes | — |
| options | no | — | |
| offset | integer | no | — |
The setups: status available (open_session works) or soon (listed, cannot be opened yet), their modes (free, challenge) and their benches by kind (status open, or soon: not offered yet).
No parameter schema on file.
Create a session (mode: free or challenge). Give open_url to the human: nothing simulates until they open it in their browser.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setup | string | yes | — |
| mode | string | yes | — |
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 arduino-cli, core or library).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| files | array | yes | — |
| run | boolean | no | — |
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, if run, starts it. files: the sources, shown read-only in the editor, never compiled. During a turn on a real bench, the bench gets it too. Prefer it to push_to_editor, which is the fallback
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| hex | string | yes | — |
| files | no | — | |
| run | boolean | no | — |
Last state (with circuit, the browser's components and wires), last compilation and the events after since_ms (2000 at most). serial is the full serial output of the current run (up to 16 KiB), reset at each compile and NOT starved by pin events: prefer it over reconstructing serial from events. During a turn on a real bench, serial and the serial events come from the bench's boa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| since_ms | number | no | — |
Change the visibility (private, link, public). Returns the viewer link; current viewers are disconnected.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| visibility | string | yes | — |
Take a place in the queue for benches of this kind (for example real or sim). The browser must be connected.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| kind | string | yes | — |
The session's place: state none, waiting (position, estimated wait eta_s) or turn (bench, end of the turn ends_at, Unix seconds).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — |
Give back the place in the queue, or the turn if it has started.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — |
End the session now, as when it expires: the place or turn ends, viewers and the browser are disconnected, everything is forgotten.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — |
The session's state without its events, cheap enough to poll: browser connected (owner), visibility, current viewer link (not renewed), viewers, created_at and expires_at (Unix seconds), run (compilations so far: event times restart at each), level and levels (null in free mode), capture ({id, kind, state} of the session's capture, logic or analog, or null). Not reported to the human's journal.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — |
Challenge mode: propose value as the answer of the current level's test test (an answer test of the level's brief). One answer per second at most. The hub checks it and returns {test, ok}; the verdict is also shown in the bench. For a hint, ask the visitor to reveal one in the bench.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| test | string | yes | — |
| value | string | yes | — |
Challenge mode: move to the next level, as the bench's "Next level" button, and only when it would be offered: every test of the current level passed and a next level exists. Returns {level, levels}, the new level (index); session_status's level changes with the bench's next state. No level skipping.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — |
Record every edge of the requested pins (probes of the setup sheet; by default the logic ones) for duration_ms (1 to 10 000 ms). In the browser's simulation, in simulated time; during the session's turn on a real bench, at the bench's logic analyser, in real time (no browser or running simulation needed then). trigger {pin, edge}: pin among pins, edge rising, falling or any; the record
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| pins | no | — | |
| duration_ms | integer | no | — |
| trigger | no | — | |
| wait_ms | integer | no | — |
| pre_ms | integer | no | — |
Sample the voltage of 1 to 4 board pins (the board's own numbers: Nano A0-A7 = 14-21, Uno A0-A5 = 14-19, Mega A0-A15 = 54-69; by default the setup's scope probes) at rate_hz (100 to 10 000) for duration_ms (1 to 10 000 simulated ms), 200 000 samples at most in all. An ADC input reads the voltage the circuit applies; any other pin, its logic level times the supply (PWM shows as a square
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| pins | no | — | |
| duration_ms | integer | no | — |
| rate_hz | integer | no | — |
State of a capture (recording, ready, failed) and its kind (logic, analog). Once ready, the measures per pin and, for a logic capture, the edges [t_us, pin, v], 2000 from offset; for an analog one, rate_hz and the samples, rows [mv_1, ...] in the order of pins (row k at k / rate_hz), 2000 rows from offset. next: the following offset, or null. t0_ms: the first sample on the session's cl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| capture | string | yes | — |
| offset | integer | no | — |
| format | string | no | — |
| from_ms | no | — | |
| to_ms | no | — |
A served setup sheet (setup.json, files included; never a solution): board, components and wires (circuit), probes, levels (without their hints: hints come through read_simulation as the visitor reveals them). Plus, when it exists, schema.png, the starting circuit as the editor draws it, as an image.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Free mode only: replace the circuit in the human's browser (the simulation stops). components: [{type, id, properties, x?, y?}] (the board is not a component), wires: [{id, start: {componentId, pinName}, end: {...}, color?, waypoints?: [{x, y}] (the wire's route, 16 points at most)}], in the shape of the setup sheet's circuit; 40 components, 120 wires, 48 KiB. The editor checks typ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — | |
| components | array | yes | — |
| wires | array | yes | — |
During the session's turn on a real bench: a photo of the bench, as an image, and t_ms, the instant of the photo in ms since the start of the turn (null when unknown). One every 2 seconds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | — | |
| agent_token | no | — |
Draft the specification of the visitor's own project with Picodev's interview: you ask the visitor, this tool says what to ask next and makes the PDF. Nothing is sent and nothing is kept. Call it with the sections written so far (none at first). sections: {id: text in simple Markdown}, ids envelope, fonctionPrincipale, fonctions, alimentation, format, environnement, production, preferences, 4000 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | no | — | |
| sections | no | — | |
| language | string | no | — |
| boolean | no | — | |
| figures | no | — |
Send Picodev the specification of the visitor's project, as a PDF, or only return its preview (send=false). sections: {id: text in simple Markdown}, ids envelope, fonctionPrincipale, fonctions, alimentation, format, environnement, production, preferences (the 8 sections of a product specification), 4000 characters at most each; a missing section reads "À préciser" (to be specified). send=false: pr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | — |
| contact | no | — | |
| sections | no | — | |
| nda | boolean | no | — |
| consent | boolean | no | — |
| send | boolean | no | — |
| session | no | — | |
| agent_token | no | — | |
| language | string | no | — |
| figures | no | — |
Send Picodev a meeting request. contact: {name, email, company?, phone?}. context: the project in a few sentences (2000 characters at most): what the visitor wants to do, where they stand, what they did in the lab. availabilities: 1 to 10 slots {from, to}, ISO 8601 dates with a time zone, within the next 60 days; or {text}, one sentence ("Tuesday mornings"). Requires consent=true. session and agen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact | yes | — | |
| context | string | yes | — |
| availabilities | yes | — | |
| consent | boolean | yes | — |
| session | no | — | |
| agent_token | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Picodev Lab or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| decode_capture | no tags | |
| list_setups | no tags | |
| open_session | state-write | state-write: declares readOnlyHint: false |
| push_to_editor | state-write | state-write: declares readOnlyHint: false |
| push_program | state-write | state-write: declares readOnlyHint: false |
| read_simulation | no tags | |
| set_visibility | state-write | state-write: declares readOnlyHint: false |
| queue_join | state-write | state-write: declares readOnlyHint: false |
| queue_status | no tags | |
| queue_leave | state-write | state-write: declares readOnlyHint: false |
| close_session | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| session_status | no tags | |
| submit_answer | state-write | state-write: declares readOnlyHint: false |
| next_level | state-write | state-write: declares readOnlyHint: false |
| capture_logic | state-write | state-write: declares readOnlyHint: false |
| capture_analog | state-write | state-write: declares readOnlyHint: false |
| read_capture | no tags | |
| read_setup | no tags | |
| push_circuit | state-write | state-write: declares readOnlyHint: false |
| bench_snapshot | state-write | state-write: declares readOnlyHint: false |
| spec_draft | no tags | |
| brief_submit | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| request_meeting | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.11.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Picodev Lab can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.