Build, check and open Arduino, ESP32 and Pico circuits with code in the Mokxi simulator.
Scored across 8 tools
Most tools are clearly distinct (list_boards, search_parts, get_part, get_project_format, validate_project). The only genuinely confusable pairs are create_code_link vs create_project (both produce editor links) and get_example vs get_project_format (both give you reference material), but the descriptions explicitly tell you which to prefer and when.
Every tool follows a consistent verb_noun snake_case pattern: create_code_link, create_project, get_example, get_part, get_project_format, list_boards, search_parts, validate_project. No style mixing or vague one-word names.
Eight tools is well-scoped for a project-building/editing domain: discovery (boards, parts), reference (format, example), validation, and two creation paths. Each tool earns its place with no filler.
The surface covers the full build lifecycle from discovery through validation to link creation, and the stateless link model means no update/delete tools are needed. Minor gap: there is no way to read back or inspect an existing project from a link, and no direct board-by-feature lookup beyond a full list.
Make a link that opens a sketch in the Mokxi editor, for code with no circuit worked out: Mokxi reads the sketch, picks the board when none is given and places and wires the parts the code names. Nothing is checked here, so prefer create_project when the wiring matters. Always give the person the link, whole and unchanged.
Inputs: code (required), board.
Make the link that opens the project in the Mokxi editor and runs it: the board, its code, and the parts and wires when there are any. Nothing is stored and no account is needed: the link carries the whole project. Refused, with the errors, while validate_project finds any. Always give the person the link, whole and unchanged.
Inputs: project (required).
A complete, working starter for a board, a part or both: a real Mokxi template as a project with its wiring and code, ready for create_project. Change it to what the person asked for instead of writing pins from memory. With no arguments, the smallest whole project.
Inputs: part, board.
One part in full: its pins with their directions, its settings with ranges and units, and how a Mokxi template wires it.
Inputs: type (required).
How to write a Mokxi project (board, parts, wires as "partId.pin" pairs, code), with the rules, the common parts and boards with their pins, and a complete example. Read this first.
Inputs: no named parameters.
Every microcontroller board Mokxi runs, with its type for the "board" field, the code it takes and its pin names.
Inputs: no named parameters.
Find Mokxi parts by what they are ("temperature sensor", "oled", "motor driver"). Returns each part's type, pins and settings, from the simulator's own catalog.
Inputs: query (required), limit.
Check a project the way the Mokxi editor does: every unknown part, wrong pin, bad setting and code problem, in plain words naming the part and pin. Fix every error, then call create_project.
Inputs: project (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Arduino benches simulated in the browser: sessions, sketch push, simulation, tests, challenges.
Electronics prototyping: real parts and pinouts, wiring checks, and shareable circuit designs.
Design perfboard and stripboard layouts, check the wiring and get a link to open them in the editor.
AI electronics blueprint generator — BOM, wiring, firmware, renders for Arduino/ESP32/RPi.
Add one secure layer between your agents and this server.