EmbeddedCI BenchPod MCP server
io.github.embeddedci-com/embeddedci-mcp·v2.13.8Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
not scanned yet
0 stars388 downloads/wk
Reviews
Write oneNobody has reviewed EmbeddedCI BenchPod yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
EmbeddedCI BenchPod tools
No tool declarations could be read from the package source. They show once the server is installed.
How EmbeddedCI BenchPod compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 58% of 1,299 Productivity servers
- Downloads a week
- 388
- more than 80% of 427 Productivity servers with a package
Release history: 15 versions in the registry since 2026-09-21, latest 2026-11-03, typically one every 2 days.
Install EmbeddedCI BenchPod in Claude Code, Cursor or VS Code
claude mcp add embeddedci-mcp -- uvx embeddedci-mcp
What the publisher says
From the EmbeddedCI BenchPod repository's README, as published. We do not edit it. Read it on GitHub
embeddedci-python
Python packages for driving an EmbeddedCI BenchPod — a hardware-in-the-loop (HIL) tester that powers a target board, flashes it over SWD, talks to its UART, I2C and CAN, and drives and measures its analog and logic signals — from pytest, from an AI agent, or from OpenHTF.
Packages
The dependency direction is strictly embeddedci-mcp → embeddedci and embeddedci-openhtf → embeddedci. All three live here so an SDK change and the matching wrapper land in one commit; each is published to PyPI on its own tag.
Versioning and stability
All three packages are on the 2.x line, the first with a stability promise:
volts, seconds and hertz; invalid arguments raise ValueError; device state comes back typed. tests/api_surface.json snapshots the public surface.
- embeddedci: everything in embeddedci.benchpod.all follows semantic versioning. Units are
(tests/tools_surface.json).
- embeddedci-mcp: tool names, input schemas and annotations are frozen for 2.x
- Consumers depend on embeddedci>=2.0,<3.
The surface snapshot tests fail on any change. When a change is intended and compatible (an addition), refresh them deliberately:
UPDATE_API_SURFACE=1 pytest packages/embeddedci/tests/test_api_surface.py
UPDATE_TOOLS_SURFACE=1 pytest packages/embeddedci-mcp/tests/test_server_runtime.py -k surfaceMigration notes: embeddedci, embeddedci-mcp, embeddedci-openhtf.
Layout
embeddedci-python/
├── pyproject.toml # uv workspace root (not published)
├── packages/
│ ├── embeddedci/ # SDK + pytest plugin
│ ├── embeddedci-mcp/ # MCP server (console script: embeddedci-mcp)
│ └── embeddedci-openhtf/ # OpenHTF plug (direct TCP/serial)
└── .github/workflows/ # CI for all packages; per-package publish tagsDevelopment
Python 3.10+.
python -m venv .venv && . .venv/bin/activate
pip install -e "packages/embeddedci[dev]" -e "packages/embeddedci-mcp[dev]" -e "packages/embeddedci-openhtf[dev]"
pytest packages/embeddedci packages/embeddedci-mcp packages/embeddedci-openhtfHardware tests skip without a pod. To run them against one:
pytest packages/embeddedci --benchpod-connection 192.168.1.213The board's I/O voltage (3.3 V) is set once in packages/embeddedci/tests/conftest.py; change it there for a 1V8 board.
Running the MCP server
# launched by an MCP client (Claude Code / Claude Desktop / Cursor) over stdio:
embeddedci-mcp --connection 192.168.1.213
# or served over HTTP for a remote bench (a token is required off loopback):
embeddedci-mcp --transport http --host 0.0.0.0 --auth-token "$TOKEN" --connection usbSee packages/embeddedci-mcp/README.md for client configuration and the tool list.
Releasing
Each package publishes from its own tag (embeddedci-v, embeddedci-mcp-v, embeddedci-openhtf-v*) via .github/workflows/publish.yml; the tag must match the version in that package's pyproject.toml. Release embeddedci first — the other two depend on it from PyPI.
The Python 3.9 placeholder
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
EmbeddedCI BenchPod: common questions
- Is EmbeddedCI BenchPod MCP server safe?
- Mostly: it is graded B (82/100). Read the EmbeddedCI BenchPod safety report
- How do I install EmbeddedCI BenchPod?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does EmbeddedCI BenchPod need an API key?
- Yes. The registry entry asks for
BENCHPOD_API_KEY. - Is EmbeddedCI BenchPod maintained?
- The last commit was 4 days ago (2026-10-31). The latest release is v2.13.8.
- What can I use instead of EmbeddedCI BenchPod?
- Servers from other publishers that do the same job: Argent MCP server, MCP Server for Excel and gflow-cli MCP server.
- How does EmbeddedCI BenchPod compare with other Productivity MCP servers?
- safety score 82/100 (higher than 58% of 1,299 Productivity servers); downloads a week 388 (more than 80% of 427 Productivity servers with a package). Full comparison.
Alternatives to EmbeddedCI BenchPod
Same job from other publishers: the closest match first, then the best rated.
- ArgentDrive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agentnot reviewedWidely usedA
- MCP Server for ExcelExcel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.not reviewedEstablishedA
- gflow-cliDrive Google Flow from an agent: Veo video and Imagen image generationnot reviewedEstablishedA
- Buoy GgLet AI agents read and drive a running React Native or Flutter app through Buoy's devtools.not reviewedEstablishedA
- Unreal EngineEngineWire: drive the Unreal Editor (UE 5.0-5.8): levels, Blueprints, UI, materials, VFX and more.not reviewedEstablishedB