Build Arduino, ESP32 and Pico circuits with code from your AI assistant. Mokxi checks the circuit and hands back a link that opens and runs it in the browser simulator.
Scored across 8 tools
Most tools target clearly distinct needs (format docs, board list, part search, part detail, validation, link creation). The main overlap is create_code_link vs create_project, both of which produce editor links, and get_example vs get_project_format, which both supply example material. The descriptions do explicitly steer between them ("prefer create_project when the wiring matters"), so confusion is limited rather than eliminated.
Every tool follows a consistent snake_case verb_noun pattern: create_code_link, create_project, get_example, get_part, get_project_format, list_boards, search_parts, validate_project. Verbs are used meaningfully and predictably across the set.
Eight tools is well within the ideal range and each one maps to a distinct step in the workflow: learn the format, look up boards/parts, grab an example, validate, then generate a link. No tool feels redundant or padded.
The surface covers the full lifecycle of building and validating a Mokxi project and emitting a shareable link, which appears to be the domain. Minor gaps exist: parts can only be found via search (no full listing), and there is no tool to inspect or re-open an existing link, but agents can work around these.
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…
Add one secure layer between your agents and this server.
