Ext Ops Panel
Open dashboard
Comparison

RunBoth vs Cloudhil

RunBoth is an MCP server published by runboth.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Cloudhil is an MCP server published by Tetef. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceRunBothCloudhil
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 0.7.0
Downloads/month (PyPI): 213
Downloads/week (PyPI): 27
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

RunBoth vs Cloudhil
FactRunBothCloudhil
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (runboth-agent-mgbxvs4loq-uc.a.run.app/mcp)On your machine (cloudhil-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/tetef/cloudhildemo
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 25 h agono remote endpoint we check

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

RunBoth

In its own words, on Official MCP Registry:

Ask runboth.dev in plain language: what RunBoth does, how to install it, and its limits.

Cloudhil

In its own words, on Official MCP Registry:

Flash pre-built STM32/LPC ELFs on real Nucleo/Discovery boards over HTTPS. Does not compile.

How to run each

RunBoth As a remote MCP server

Claude Code
claude mcp add --transport http agent https://runboth-agent-mgbxvs4loq-uc.a.run.app/mcp

Cloudhil As a local MCP server: PyPI package

Claude Code
claude mcp add --env "CLOUDHIL_API_KEY=<YOUR_CLOUDHIL_API_KEY>" --transport stdio cloudhil -- uvx cloudhil-mcp

Requires: CLOUDHIL_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only RunBoth has a remote endpoint we check. How we check endpoints

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

What it can do: RunBoth · What it can do: Cloudhil · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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