Ext Ops Panel
Open dashboard
Comparison

duck-duck-duck vs ExecBro

duck-duck-duck is a plugin bundle for AI coding tools published by ideo. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ExecBro is an MCP server published by execbro.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. 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
Marketplaceduck-duck-duckExecBro
Claude Code: claude-plugins-community Listed
Version: 4
Forks (GitHub): 2
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.18.0
Downloads/month (npm): 4 348
Downloads/week (npm): 651
Forks (GitHub): 9
Stars (GitHub): 79
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.17.1
Downloads/month (npm): 4 348
Downloads/week (npm): 651
Forks (GitHub): 9
Stars (GitHub): 79
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

duck-duck-duck vs ExecBro
Factduck-duck-duckExecBro
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)25 (worse)79 (better)
Forks (GitHub) (differs)2 (worse)9 (better)
Last release (differs)Not published2026-10-20
Where it runs (differs)Installs as a plugin bundleOn your machine (execbro)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)8Not published
Parts of the bundle (differs)8Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/ideo/rubber-duckgithub.com/igorzheludkov/execbro
Changes in the last 7 days (differs)05
First seen2026-10-112026-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

duck-duck-duck

In its own words, on Claude Code: claude-plugins-community:

A coding companion that watches your Claude Code sessions and reacts with voice, animations, and optional physical hardware. Scores every prompt and response on-device via Apple Foundation Models — private and free by default. Speaks opinionated reactions, handles permissions by voice, and picks from 10 expressive voices based on the mood of the code. Requires the free Duck Duck Duck macOS companion app (Apple Silicon, macOS 26+). Plugin is located in the plugin/ subdirectory of the repository.

ExecBro

In its own words, on Official MCP Registry:

Gives AI agents eyes and hands into running React Native apps: logs, REPL, tap, screenshots

How to run each

duck-duck-duck As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install duck-duck-duck@claude-community

ExecBro As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio execbro -- npx -y execbro

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

What it can do: duck-duck-duck · What it can do: ExecBro · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.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