Ext Ops Panel
Open dashboard
Comparison

Effect vs esp32-ai-agent-skill

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). esp32-ai-agent-skill is a plugin bundle for AI coding tools published by ezrover. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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
MarketplaceEffectesp32-ai-agent-skill
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 12 871
Stars (Docker Hub): 0
Stars (GitHub): 239
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 10
Stars (GitHub): 44
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

Effect vs esp32-ai-agent-skill
FactEffectesp32-ai-agent-skill
Marketplaces that list it11
Stars (GitHub) (differs)239 (better)44 (worse)
Pulls (Docker Hub) (differs)12 871No figure on Docker Hub
Forks (GitHub) (differs)13 (better)10 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/effect-mcp)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)MITNot stated
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/ezrover/esp32-ai-agent-skill
Changes in the last 7 days00
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

Effect

In its own words, on Docker MCP Catalog:

Tools and resources for writing Effect code in Typescript.

esp32-ai-agent-skill

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

Expert ESP32 embedded systems plugin for Claude Code and Cowork. Provides chip selection guidance across 9 ESP32 variants (ESP32, S2, S3, C3, C6, H2, C5, P4, C61), GPIO pin validation with anti-bricking safety checks (strapping pins, flash-connected pins, ADC2/WiFi conflicts), Arduino and ESP-IDF code generation, LVGL v8.2-v9.5 UI reference docs, and 60+ Waveshare board pinouts. Includes 50 automated tests. The first hardware/embedded Claude Code plugin.

How to run each

Effect As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio effect-mcp -- docker run -i --rm mcp/effect-mcp

esp32-ai-agent-skill As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install esp32-ai-agent-skill@claude-community

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

Tools each declares

The marketplaces of esp32-ai-agent-skill publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Effect · What it can do: esp32-ai-agent-skill · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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