Skip to main content
Glama

Server Details

Arduino benches simulated in the browser: sessions, sketch push, simulation, tests, challenges.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
PICODEV-SAS/picodev-lab-plugin
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 23 tools

Disambiguation4/5

Most tools have clearly distinct targets: session lifecycle, queueing, captures, simulation state, challenges, and Picodev intake are separated by resource and action. The main possible confusion is push_program vs push_to_editor, which is explicitly framed as fallback behavior, and brief_submit/spec_draft/request_meeting all involve visitor contact and consent but serve different workflows.

Naming Consistency3/5

All names use snake_case, but the verb/noun order is mixed: many are verb_noun (open_session, push_circuit, read_capture), while others are noun_verb or noun_noun (bench_snapshot, brief_submit, queue_join, session_status, spec_draft). The naming remains readable, but the convention is not predictable enough for a top score.

Tool Count3/5

23 tools is on the heavy side and reflects several broad subdomains: real-bench sessions, simulation control, capture analysis, challenge mode, specification drafting, and meeting requests. Each tool has a plausible role, but the overall surface feels large and somewhat borderline for a single MCP server.

Completeness4/5

The surface covers the major workflows well: session setup and teardown, queueing, circuit/program delivery, simulation reading, logic/analog capture, decoding, challenge progression, and Picodev project/meeting submission. There are minor gaps around explicit run/pause/serial-input control and capture cancellation, but agents can mostly work around them through existing tools.

Available Tools

23 tools
bench_snapshotBench photoCInspect

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.

Inputs: session, agent_token.

brief_submitSend the spec to PicodevAInspect

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: preview, nothing is sent, contact and consent are not required. send=true: requires contact {name, email, company?, phone?} and consent=true. nda=true: the visitor wants a non-disclosure agreement first; without sections, only contact and title are sent, without PDF. session and agent_token, optional: the mail also says what the visitor did in the lab. language: fr or en, the PDF's headings. sections.contact and figures: as for spec_draft (refused with nda=true, as sections). Write the sections with spec_draft first. Before passing consent=true, show the visitor the consent text in the visitor's language, and wait until they accept it. In French: "J'accepte que mes coordonnées et la description de mon projet soient envoyées à Picodev par courriel, pour qu'ils me répondent. Picodev les garde 3 ans après le dernier échange et ne les utilise pour rien d'autre. Détails : lab.picodev.fr/confidentialite" In English: "I agree that my contact details and the description of my project are sent to Picodev by e-mail, so that they can answer me. Picodev keeps them for 3 years after our last exchange and uses them for nothing else. Details: lab.picodev.fr/en/privacy" Returns {sent, filename, pdf (base 64, absent with nda), missing (empty or too short sections), next (a sentence for the visitor, to say in their language)}}: write the PDF on the visitor's machine.

Inputs: title (required), nda, send, consent, +6 more.

capture_analogCapture analog signalsAInspect

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 wave). Simulation only: refused during a turn on a real bench, whose analyser has no analog channel. Read the result with read_capture.

Inputs: pins, rate_hz, session, agent_token, +1 more.

capture_logicCapture logic signalsAInspect

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 recording then lasts wait_ms + duration_ms (10 000 ms at most) and keeps pre_ms (0 to wait_ms) before the first matching edge within wait_ms and duration_ms after it; with no such edge, the whole recording. Read the result with read_capture, decode it with decode_capture.

Inputs: pins, pre_ms, session, trigger, +3 more.

close_sessionClose the sessionA
Destructive
Inspect

End the session now, as when it expires: the place or turn ends, viewers and the browser are disconnected, everything is forgotten.

Inputs: session, agent_token.

decode_captureDecode a captureA
Read-only
Inspect

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. Returns {capture, protocol, frames, next, problems}, 2000 frames from offset. uart frames {t_us, value, error?} (framing, parity) and text, the printable bytes of the page; spi {t_us, mosi?, miso?} per word, while cs is low when given; i2c {t_us, kind (start, restart, address, data, stop), value?, rw?, ack?}. problems: what makes the decoding doubtful.

Inputs: capture (required), channels (required), protocol (required), offset, +3 more.

list_setupsList setupsA
Read-only
Inspect

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).

Inputs: no named parameters. Returns: result

next_levelNext levelAInspect

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.

Inputs: session, agent_token.

open_sessionOpen a sessionAInspect

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

Inputs: mode (required), setup (required).

push_circuitPush a circuitAInspect

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 types and pins: read the outcome with read_simulation (circuit, circuit_error). 6 per minute.

Inputs: wires (required), components (required), session, agent_token. Returns: result

push_programPush a compiled programAInspect

Send a program compiled on the visitor's machine (Intel HEX text, 48 KiB at most, e.g. arduino-cli's .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 when the local toolchain is missing.

Inputs: hex (required), run, files, session, +1 more. Returns: result

push_to_editorPush sources to the editorAInspect

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).

Inputs: files (required), run, session, agent_token. Returns: result

queue_joinJoin the bench queueBInspect

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

Inputs: kind (required), session, agent_token.

queue_leaveLeave the bench queueBInspect

Give back the place in the queue, or the turn if it has started.

Inputs: session, agent_token.

queue_statusQueue statusB
Read-only
Inspect

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

Inputs: session, agent_token.

read_captureRead a captureA
Read-only
Inspect

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 clock (ms since the simulation's launch, or since the start of the turn on a real bench), null when unknown; t_us and rows count from the capture's start. format="png": the same without edges or samples, plus a chart of the signals as an image (from_ms and to_ms, from the capture's start, to zoom; 4 per minute).

Inputs: capture (required), to_ms, format, offset, +3 more.

read_setupRead a setupA
Read-only
Inspect

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.

Inputs: id (required).

read_simulationRead the simulationB
Read-only
Inspect

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 board (since the turn began or the last compile), t on the turn's clock. In challenge mode: the level's brief and its results. circuit_modified: the circuit differs from the setup sheet's (types, ids, properties, wires; not positions or colours), null when unknown. circuit_error: the editor's last refusal of a pushed circuit, returned once.

Inputs: session, since_ms, agent_token.

request_meetingRequest a meeting with PicodevAInspect

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 agent_token, optional: the mail also says what the visitor did in the lab. Before passing consent=true, show the visitor the consent text in the visitor's language, and wait until they accept it. In French: "J'accepte que mes coordonnées et la description de mon projet soient envoyées à Picodev par courriel, pour qu'ils me répondent. Picodev les garde 3 ans après le dernier échange et ne les utilise pour rien d'autre. Détails : lab.picodev.fr/confidentialite" In English: "I agree that my contact details and the description of my project are sent to Picodev by e-mail, so that they can answer me. Picodev keeps them for 3 years after our last exchange and uses them for nothing else. Details: lab.picodev.fr/en/privacy" Returns {sent, next}: Picodev answers by e-mail to confirm a slot.

Inputs: consent (required), contact (required), context (required), availabilities (required), +2 more.

session_statusSession statusB
Read-only
Inspect

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.

Inputs: session, agent_token.

set_visibilitySet visibilityAInspect

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

Inputs: visibility (required), session, agent_token.

spec_draftDraft a project specA
Read-only
Inspect

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 characters at most each. sections.contact, optional: the contact details the visitor wants printed at the end of the document (1000 characters at most; not part of the interview's progress). language: fr or en, the one the visitor answers in (headings, look_for and questions, the PDF). pdf=true: also the PDF, with Picodev Lab's template; requires title (one line). figures, with pdf=true, optional: the drawings the visitor approved, 3 at most, each {section (a section id), caption (one line), type (png or svg), data (base 64, 200 KiB at most decoded)}, placed after their section's text; an SVG loads nothing (no script, no DTD, href # or data:image/ only). Returns {rules (how to run the interview: follow them), sections [{id, heading, required, state (empty, thin, filled), look_for and questions while not filled}], next (the section to ask about, or null), ready (the four required sections filled: enough for Picodev to start), filename and pdf (base 64) with pdf=true}.

Inputs: pdf, title, figures, language, +1 more.

submit_answerSubmit an answerBInspect

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.

Inputs: test (required), value (required), session, agent_token.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects any MCP client to a deterministic in-browser Docker simulation so a user's own AI can teach by inspecting and mutating world state, rewinding and comparing events, running 27 "what-if" experiments, tracing concept relationships, and quizzing the learner. It exposes 14 typed tools over Streamable HTTP with bearer-token auth, needing no hosted AI or server-side lab state.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables running code against tests in an isolated sandbox to obtain PASS/FAIL verdicts with signed, offline-checkable certificates, and generating verified code with attached certificates after execution against derived tests.
      2
      37 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Let coding agents play, test and tune your 2D web game. The debuff MCP server attaches to the game you have open (or runs a headless copy) and gives agents live state, explained and source-mapped errors, frame timings, typed params, deterministic replays and rewind, scenario tests and fuzz playtesting. Everything an agent does shows in your dev panel, where you can undo it.
      21
      12
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.