impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Design circuits, simulate and verify embedded firmware, and lay out PCBs with AI agents.
Skills that teach the AI this kind of work; they work alongside this one
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Create beautiful slides on the web using a coding agent's frontend skills
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 28/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 48/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 5/5 checks · What you ask goes through the maker’s server (api.labwired.com) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
LabWiredhttps://api.labwired.com/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsLabWired
Use LabWired and tell me what you can do for me, then show me one thing✓ If Claude says it is using LabWired or shows a LabWired tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
LabWiredhttps://api.labwired.com/mcpStart a new chat and pick LabWired from your plugins before typing
Use LabWired and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using LabWired or shows a LabWired tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user labwired https://api.labwired.com/mcpYou should see LabWired listed as connected
Use LabWired and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using LabWired or shows a LabWired tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use LabWired and tell me what you can do for me, then show me one thing✓ If Cursor says it is using LabWired or shows a LabWired tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use LabWired and tell me what you can do for me, then show me one thing✓ If VS Code says it is using LabWired or shows a LabWired tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://api.labwired.com/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user labwired https://api.labwired.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"labwired": {
"url": "https://api.labwired.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"labwired": {
"type": "http",
"url": "https://api.labwired.com/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 16, 2026
The registry name was verified with the GitHub account w1ne, which owns the repo
Code last changed yesterday
Uses MIT
Responded in 1051 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/w1ne-labwired)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed yesterday, and the latest version (0.1.0) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Pascal 3D Editor, Figma MCP Server, Remocn: Remotion MCP server, Harness, ChatCut
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
Start Claude Code and Codex agents the person can watch, wait for them and read their answers.
AI video editor for agents: cut footage, add captions and motion graphics, export editable edits.
| This one LabWired | Pascal 3D Editor | Figma MCP Server | Remocn: Remotion MCP server | Harness | ChatCut | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | Yes | No | No | No |
| Basic checks | 5/5 | 5/5 | 4/4 | 4/4 | 3/3 | 4/4 |
| License | MIT | MIT | – | MIT | MIT | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Run your firmware on a virtual instance of a real chip, from your terminal, your CI, or your AI coding agent. No board on your desk.
Recorded from docs/assets/demo.tape against a real binary. You can re-run it. The second half breaks an assertion on purpose, so you can see the gate fail.
LabWired Core loads a firmware ELF and executes it against modeled silicon: CPU, buses, peripherals, sensors, displays, and protocol devices. You get UART output, GPIO and bus traces, register state, and a pass/fail exit code.
Runs are deterministic. The same ELF and the same board manifest give the same trace on every machine. That is what makes a simulator run usable as a CI gate.
Supported cores:
This repository is the engine behind labwired.com. The hosted browser Playground and the hosted MCP connector run the same models. To look before installing anything, open a lab: SSD1306 hello, U575 Star Catcher, BME280 weather, or IO-Link DI/DO.
Testing firmware on real boards is slow. You wait for hardware, you flash it, and when something breaks you get a dark LED and no trace. Do that for every board in a product line and a hardware CI bench stops being worth the upkeep.
LabWired runs the same binary you would flash. You assert on what the firmware made the hardware do.
Two things separate it from a CPU emulator.
The board is modeled, not only the chip. Sensors, displays, and bus devices live in the system manifest. You can assert on I2C traffic, SPI framing, or what a panel was told to draw.
We publish where the model is thin. Every capability sits in a named tier. Anywhere the simulator short-circuits real hardware, we write it down in the Fidelity Ledger. You cannot gate on a simulator you cannot audit.
Clone the repository, install the CLI, run a firmware. No cross-toolchain needed.
git clone https://github.com/w1ne/labwired-core && cd labwired-core
curl -fsSL https://labwired.com/install.sh | LABWIRED_VERSION=v0.25.0 sh labwired test --script examples/nrf54l15-dk/io-smoke.yaml
nRF54L15 boot OK core=cortex-m33 rram=1524K ram=256K uarte20@0x500C6000 gpio2@0x50050400 regs from MDK/SVD, not nRF52 PASS 4/4 checks · io-smoke · 200000 steps · 0.04s
That is a committed bare-metal ELF booting on an nRF54L15-DK profile in under a second. Nothing is compiled on your machine.
The four checks are the three UART lines plus the stop reason.
The firmware prints those lines from string literals. The text proves nothing by itself. What it proves is that the bytes arrived. To send them, the firmware had to boot from RRAM at 0x0, set up RAM at 0x20000000, and drive UARTE20 over EasyDMA. Get the UARTE base wrong in the chip model and you get no output at all.
GPIO is checked at the pin, not in the banner, by firmware_survival::test_nrf54l15_lights_dk_led0. The example README says why both tests are needed.
The verdict goes to stderr. The exit code is the gate: 0 passes, anything else fails. UART output and --json stay on stdout, so pipes keep working.
The install script covers Linux, macOS, and Windows via WSL2.
curl -fsSL https://labwired.com/install.sh | LABWIRED_VERSION=v0.25.0 sh
| Variable | Effect |
|---|---|
LABWIRED_VERSION= | pin a release |
LABWIRED_INSTALL_DIR= | choose the install directory |
LABWIRED_FROM_SOURCE=1 | build from source instead of downloading |
To read the installer before running it:
curl -fsSL https://labwired.com/install.sh -o install.sh # review it, then:
sh install.sh
There is a native Windows build — labwired.exe and labwired-dap.exe — but no install script for it; the archive is unpacked by hand. PowerShell 5.1 and later have tar built in.
$v = "v0.25.0"
Invoke-WebRequest "https://github.com/w1ne/labwired-core/releases/download/$v/labwired-$v-windows-x86_64.tar.gz" -OutFile labwired.tar.gz mkdir $env:LOCALAPPDATA\LabWired -Force tar -xzf labwired.tar.gz -C $env:LOCALAPPDATA\LabWired $env:PATH += ";$env:LOCALAPPDATA\LabWired" labwired --version
The VS Code extension does this for you on Windows — it downloads the same archive on first use. WSL2 also works and takes the Linux instructions above.
Or build it yourself:
cargo build --release -p labwired-cli
labwired run --chip configs/chips/<chip>.yaml --firmware path/to/firmware.elf
labwired test --script path/to/test.yaml --junit report.xml
run is interactive: UART, GPIO, traces, snapshots.
test is the gate. It writes result.json, uart.log, and JUnit, and returns an exit code. Assertions cover UART content, memory and register values, stop reasons, and step and wall-time limits.
See the CLI reference and the test runner reference.
Use labwired.Sim to run an ELF, wait for UART output, and write pytest checks:
from labwired import Sim
with Sim("tests/fixtures/uart-ok-thumbv7m.elf", chip="ci-fixture-cortex-m3-uart1", uart="uart1") as sim: sim.expect("OK", timeout="1ms")
The SDK runs the Rust engine in your Python process. Start with the Python SDK quickstart for source installation and a runnable pytest test. This SDK is not yet published to PyPI.
The same YAML scripts are the merge gate, with no HIL bench to maintain:
- run: labwired test --script examples/ci/uart-ok.yaml --junit report.xml
See CI integration and labwired.com/ci.
LabWired speaks MCP. An agent can assemble a board, run firmware, and read the result back. You never touch the toolchain.
claude mcp add labwired --transport http https://api.labwired.com/mcp
codex mcp add labwired --url https://api.labwired.com/mcp
Your client opens a browser to sign in on first use. Other MCP clients take the standard block:
{ "mcpServers": { "labwired": { "type": "http", "url": "https://api.labwired.com/mcp" } } }
Then ask for what you want:
*"Connect LabWired over MCP. Load a virtual STM32 LED + UART board, run the firmware,
check the UART output, and give me the Playground URL."*
Agents working inside this repository should read docs/agents.md.
A board is data, not code.
A chip descriptor in configs/chips declares memory geometry, cores, and peripheral bases. A system manifest in configs/systems wires up pins, buses, and the devices on them. Firmware writes to modeled registers. The modeled hardware drives the firmware back.
To add a board you write those two files and an example. You do not patch the engine. See the board onboarding playbook and the configuration reference.
Every capability sits in one of three tiers, and we say which:
The NUCLEO-H563ZI example is the reference case. The same firmware runs on a physical board and on the simulator, and the artifacts are committed. See VALIDATION.md, determinism_report_h563.json, and the golden reference method.
Each report covers the scope it describes. None of them claim that every instruction and timing path matches silicon. The Fidelity Ledger has both sides: where we short-circuit hardware, and where we hold up. One e-paper panel matches silicon on 19033 of 19033 SPI transfers.
ARM Cortex-M and RISC-V have the deepest coverage. Some ESP32/Xtensa paths exist for specific examples. The optional native QEMU-derived Cortex-A7 backend runs bounded instruction fixtures through the same CPU and bus interfaces. The Luckfox Pico Mini A dossier includes vendor assets, pins and declared memory geometry; RV1103 peripherals and Linux boot remain unimplemented.
Check the per-board status before you assume a peripheral is modeled. It is in docs/boards, the validation status matrix, and the browsable catalog at app.labwired.com/validation.
| To see | Run |
|---|---|
| A deterministic pass/fail gate | CI UART smoke |
| Firmware driving a sensor over I2C | Blinky + TMP102 |
| Simulator compared against a physical board | [NUCLEO-H563ZI](examples/nucleo-h563z