Effect vs design-council
design-council is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). design-council is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Effect | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a0e077abc890 Forks (GitHub): 13 Pulls (Docker Hub): 13 073 Stars (Docker Hub): 0 Stars (GitHub): 238 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-kit | Not listed | Removed on 2026-10-16 Version: 0.6.0 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
| Community marketplace iowarp/clio-coder | Not listed | Removed on 2026-10-23 Version: 0.6.1 Forks (GitHub): 5 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
| Fact | Effect | design-councilno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 238 | 8 |
| Pulls (Docker Hub) (differs) | 13 073 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 13 | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/effect-mcp) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/tim-smart/effect-mcp | github.com/iowarp/clio-coder |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of design-council
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Collaborative technical discussion with proactive requirements gathering
-
DCVE methodology for systematic project planning, and Discuss for multi-perspective debate and decision-making — both powered by Claude Code agent teams
-
Consulting engagement orchestrator where action fields are the work-breakdown-structure containers for every deliverable: each deliverable runs its own design-thinking loop…
-
Multi-perspective plan review with VP Product, VP Engineering, and VP Design for implementation plans and architecture proposals.
-
Convene a team of specialist agents out of a 20-agent roster in a 3-round deliberation council on your hardest engineering decisions. Walk away with a unified design and a phased…
-
Guided development workflow: task decomposition, planning, peer plan review, browser plan approval, implementation, tidy, check/test, rules and code review, one commit per build…
What each says it does
Effect
Tools and resources for writing Effect code in Typescript.
design-council
Convenes several expert perspectives that challenge each other on a design decision with real trade-offs before code is written; quick mode runs a single round. Not for a one-question-at-a-time interrogation of a plan; use grill-me. Not for splitting implementation across workers; use dispatch directly.
How to run each
Effect As a local MCP server: Docker image
claude mcp add --transport stdio effect-mcp -- docker run -i --rm mcp/effect-mcpdesign-council
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 design-council 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: design-council · 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.