Ext Ops Panel
Open dashboard
Comparison

automotive vs EmbeddedCI BenchPod

automotive is a plugin bundle for AI coding tools published by MathWorks. Marketplaces we read that list it: 1 (Community GitHub marketplaces). EmbeddedCI BenchPod is an MCP server published by embeddedci-com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceautomotiveEmbeddedCI BenchPod
Community marketplace matlab/matlab-agentic-toolkit Listed
Version: 0.5.0
Forks (GitHub): 148
Stars (GitHub): 1 276
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.13.9
Downloads/month (PyPI): 1 509
Downloads/week (PyPI): 865
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 2.13.9
Downloads/month (PyPI): 1 509
Downloads/week (PyPI): 865
Forks (GitHub): 0
Stars (GitHub): 0
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

automotive vs EmbeddedCI BenchPod
FactautomotiveEmbeddedCI BenchPod
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 276 (better)0 (worse)
Forks (GitHub) (differs)148 (better)0 (worse)
Last release (differs)2026-11-06 (worse)2026-11-07 (better)
Where it runs (differs)Installs as a plugin bundleOn your machine (embeddedci-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/matlab/matlab-agentic-toolkitgithub.com/embeddedci-com/embeddedci-python
Changes in the last 7 days (differs)25
First seen (differs)2026-10-272026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

automotive

In its own words, on Community GitHub marketplaces:

Automated Driving Toolbox, Computer Vision Toolbox, RoadRunner, RoadRunner Scenario, RoadRunner Scene Builder, Sensor Fusion and Tracking Toolbox, Vehicle Dynamics Blockset, Automated Driving Toolbox Interface for Eclipse SUMO Traffic Simulator, and Scenario Builder for Automated Driving Toolbox.

EmbeddedCI BenchPod

In its own words, on Official MCP Registry:

Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.

How to run each

automotive As a Claude Code plugin

Claude Code
/plugin marketplace add matlab/matlab-agentic-toolkit
/plugin install automotive@matlab-agentic-toolkit

EmbeddedCI BenchPod As a local MCP server: PyPI package

Claude Code
claude mcp add --env "BENCHPOD_API_KEY=<YOUR_BENCHPOD_API_KEY>" --transport stdio embeddedci-mcp -- uvx embeddedci-mcp

Requires: BENCHPOD_API_KEY (secret)

Commands 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 automotive publish no settings it asks for, so we do not compare settings.

What it can do: automotive · What it can do: EmbeddedCI BenchPod · 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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built