Ext Ops Panel
Open dashboard
Comparison

Effect vs MetaForge (local)

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). MetaForge (local) is a plugin bundle for AI coding tools published by MetaForge. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
MarketplaceEffectMetaForge (local)
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 12 972
Stars (Docker Hub): 0
Stars (GitHub): 238
Not marked · First seen
Not listed
Community marketplace fidelodok/metaforge Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 8
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 MetaForge (local)
FactEffectMetaForge (local)
Marketplaces that list it11
Stars (GitHub) (differs)238 (better)8 (worse)
Pulls (Docker Hub) (differs)12 972No figure on Docker Hub
Forks (GitHub) (differs)13 (better)0 (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 for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle59
Licence (differs)MITApache-2.0
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/fidelodok/metaforge
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-18

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.

MetaForge (local)

In its own words, on Community GitHub marketplaces:

Runs MetaForge as a local process over stdio. No gateway, no account, no network. Needs the `metaforge-mcp` command on your PATH; the package README gives the one line that installs it.

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

MetaForge (local) As a Claude Code plugin

Claude Code
/plugin marketplace add fidelodok/metaforge
/plugin install metaforge-local@metaforge

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

Tools each declares

The marketplaces of MetaForge (local) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Effect publish no settings it asks for, so we do not compare settings.

What it can do: Effect · What it can do: MetaForge (local) · 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