Ext Ops Panel
Open dashboard
Comparison

Effect vs quick-question

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). quick-question is a plugin bundle for AI coding tools published by tykisgod. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
MarketplaceEffectquick-question
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 12 837
Stars (Docker Hub): 0
Stars (GitHub): 239
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.17.0
Forks (GitHub): 2
Stars (GitHub): 12
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 quick-question
FactEffectquick-question
Marketplaces that list it11
Stars (GitHub) (differs)239 (better)12 (worse)
Pulls (Docker Hub) (differs)12 837No figure on Docker Hub
Forks (GitHub) (differs)13 (better)2 (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
Hooks it runs (differs)Not published13
Parts of the bundle (differs)Not a bundle30
LicenceMITMIT
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/tykisgod/quick-question
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.

quick-question

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

Unity Agent Harness for Claude Code. Auto-compiles C# on every edit, runs EditMode/PlayMode test pipelines with error checking, and performs deep code review using Claude subagents — with each finding independently verified against source before fixing. Includes tykit, an HTTP server inside Unity Editor for AI agent control (run tests, play/stop, read console, inspect GameObjects). 20 slash commands covering the full dev loop from edit to ship. Optional cross-model review via Codex CLI for teams that want multi-model verification. macOS, Unity 2021.3+.

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

quick-question

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of quick-question 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: quick-question · 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