Ext Ops Panel
Open dashboard
Comparison

Effect vs han-atlassian

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). han-atlassian is a plugin bundle for AI coding tools published by testdouble. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. 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
MarketplaceEffecthan-atlassian
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 13 508
Stars (Docker Hub): 0
Stars (GitHub): 238
Not marked · First seen
Not listed
Community marketplace testdouble/han Not listed Listed
Version: 2.3.1
Forks (GitHub): 28
Stars (GitHub): 342
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 han-atlassian
FactEffecthan-atlassian
Marketplaces that list it11
Stars (GitHub) (differs)238 (worse)342 (better)
Pulls (Docker Hub) (differs)13 508No figure on Docker Hub
Forks (GitHub) (differs)13 (worse)28 (better)
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 bundle6
Licence (differs)MITNot stated
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/testdouble/han
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-08

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.

han-atlassian

In its own words, on Community GitHub marketplaces:

Atlassian-facing extensions to the Han suite. Adds markdown-to-confluence, which publishes a local Markdown file to a user-specified Confluence page; project-documentation-to-confluence, which runs the han-documentation project-documentation skill and then publishes the result there; investigate-to-confluence, which runs the core investigate skill and publishes the resulting investigation report there; code-overview-to-confluence, which runs the core code-overview skill and publishes the resulting overview there; plan-a-feature-to-confluence, which runs the core plan-a-feature skill and publishes the spec and its companion artifacts there as a page tree; and work-items-to-jira, which creates one Jira ticket per slice from a work-items file. All work through the Atlassian MCP server. Depends on han-core, han-documentation, han-planning, and han-coding (its wrapper skills run skills from each and its wrapped skills dispatch the shared han-core agents), and on han-communication (its wrapped prose-producing skill

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

han-atlassian As a Claude Code plugin

Claude Code
/plugin marketplace add testdouble/han
/plugin install han-atlassian@han

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

Tools each declares

The marketplaces of han-atlassian 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: han-atlassian · 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