Developer Tools

picodev.fr

Manages browser-based electronics lab sessions, allowing code and compiled firmware to be pushed to simulated circuits and reading simulation state.

1 endpoint21 known toolsFirst detected October 22, 2026Last detected October 22, 2026

ENDPOINT 1

https://lab.picodev.fr/mcp

No auth detected

MCP server metadata

Name: picodev-lab-hub

Capabilities

promptsresourcestools

Server instructions

Picodev Lab: open a session with open_session, give open_url to the human so they open it in their browser (they run the simulation), then compile the code locally and send it with push_program (push_to_editor, where the lab compiles, only when the toolchain is missing), and read the simulation.

Known tools 21

list_setups

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

Inferred read-only

open_session

Create a session (mode: free or challenge).

Potential side effects

push_to_editor

Replace the code in the human's browser and, if run, compile it in the lab's cloud and start it.

Inferred read-only

push_program

Send a program compiled on the visitor's machine (Intel HEX text, 48 KiB at most, e.

Potential side effects

read_simulation

Last state (with circuit, the browser's components and wires), last compilation and the events after since_ms (2000 at most).

Inferred read-only

set_visibility

Change the visibility (private, link, public).

Inferred read-only

queue_join

Take a place in the queue for benches of this kind (for example real or sim).

Inferred read-only

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

Inferred read-only

queue_leave

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

Inferred read-only

close_session

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

Inferred read-only

session_status

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

Inferred read-only

next_level

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.

Inferred read-only

capture_logic

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

Inferred read-only

capture_analog

Sample the voltage of 1 to 4 board pins (0-13 digital, 14-21 = A0-A7; 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.

Inferred read-only

read_capture

State of a capture (recording, ready, failed) and its kind (logic, analog).

Inferred read-only

read_setup

A served setup sheet (setup.

Inferred read-only

push_circuit

Free mode only: replace the circuit in the human's browser (the simulation stops).

Inferred read-only

bench_snapshot

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

Inferred read-only

spec_draft

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.

Inferred read-only

brief_submit

Send Picodev the specification of the visitor's project, as a PDF, or only return its preview (send=false).

Potential side effects

request_meeting

Send Picodev a meeting request.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.picodev-lab-hub]
url = "https://lab.picodev.fr/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "picodev-lab-hub": {
      "type": "http",
      "url": "https://lab.picodev.fr/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: picodev-lab-hub
Remote MCP URL: https://lab.picodev.fr/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "picodev-lab-hub": {
      "url": "https://lab.picodev.fr/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "picodev-lab-hub": {
      "type": "http",
      "url": "https://lab.picodev.fr/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "picodev-lab-hub",
  "transport": "streamable-http",
  "url": "https://lab.picodev.fr/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.