Ext Ops Panel
Open dashboard
Comparison

Effect vs kumi

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). kumi is a plugin bundle for AI coding tools published by annavetech. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
MarketplaceEffectkumi
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 12 910
Stars (Docker Hub): 0
Stars (GitHub): 239
Not marked · First seen
Not listed
Community marketplace davepoon/buildwithclaude Not listed Listed
Version: 1.5.0
Forks (GitHub): 0
Stars (GitHub): 1
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 kumi
FactEffectkumi
Marketplaces that list it11
Stars (GitHub) (differs)239 (better)1 (worse)
Pulls (Docker Hub) (differs)12 910No figure on Docker Hub
Forks (GitHub) (differs)13 (better)0 (worse)
Last release (differs)Not published2026-10-16
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
Hooks it runs (differs)Not published12
Parts of the bundle (differs)Not a bundle50
LicenceMITMIT
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/annavetech/kumi
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-15

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.

kumi

In its own words, on Community GitHub marketplaces:

A coordinated engineering team of named AI specialists that remembers your project between sessions. Call yui to route work, or call any specialist directly: Go (jaan, siim, mart), Angular (liis, kadi, tiiu), iOS (ren, shu, ryo), Python (eero, anu, ivo), React (noa, rui, aki), SQL (saku), NoSQL (remo), architecture for any stack (kai), process management (enn), and DevOps/infra (sora). Each ships as both a skill and a subagent. Bundled hooks capture finished work when a session ends and say at the next session start that saved work exists, and record per-session and per-agent token and time usage. Every specialist follows the same discipline: read context first, make the smallest correct change, verify.

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

kumi As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install kumi@buildwithclaude

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

Tools each declares

The marketplaces of kumi 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: kumi · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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