s32 vs BLEA
s32 is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
s32 is a plugin bundle for AI coding tools published by Open-source contributors. No marketplace we read lists it any more. BLEA is an MCP server published by Nitmi. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  BLEA | |
|---|---|---|
| Community marketplace bigbangten/s32ds-mcp-bridge | Removed on 2026-10-18 Version: 0.4.3 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.0 Downloads/month (PyPI): 423 Downloads/week (PyPI): 55 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 0.6.1 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | s32no longer listed · | BLEA |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 3 | 12 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (blea) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | 8 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bigbangten/s32ds-mcp-bridge | github.com/nitmi/blea |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of s32
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Hardware and EDA toolkit. Drives the KiCad CLI for schematic/PCB export and checks, and OpenSCAD for parametric 3D/2D part design and STL/DXF/PNG output.
-
On-target debugging for Cortex-M: SWD and JTAG probes, HardFault decoding, GDB, ITM and SWO trace, and DWT timing.
-
AI-native MCU debugging and observability through probes, symbols, RTOS, logs, and build tools.
-
Build an MCP server and bundle your tools into a shareable plugin, end to end. Two skills: build-mcp scaffolds one server; build-plugin packages skills, hooks, agents, and MCP…
-
External tools integration skills for CLI utilities, APIs, and third-party services
-
PIO Agent builds, flashes, tests, and monitors PlatformIO firmware safely from Codex using PlatformIO MCP.
What each says it does
s32
Live introspection bridge for NXP S32 Design Studio 3.5.x. Provides /s32 slash commands, MCP tools, DSF-aware debug control, and a self-improving skill that verifies against the running workbench.
BLEA
Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.
How to run each
s32
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
BLEA As a local MCP server: PyPI package
claude mcp add --transport stdio blea -- uvx blea mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of BLEA publish no settings it asks for, so we do not compare settings.
What it can do: s32 · What it can do: BLEA · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.