Ext Ops Panel
Open dashboard
Comparison

Effect vs architecture

architecture is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). architecture 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-19. 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

Where each is published
MarketplaceEffectarchitecture
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 12 969
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.4.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

Effect vs architecture
FactEffectarchitectureno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)2388
Pulls (Docker Hub) (differs)12 969No figure on Docker Hub
Forks (GitHub) (differs)135
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
Licence (differs)MITApache-2.0
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/iowarp/clio-coder
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-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 architecture

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • architecture-suite

    Understand the system you have and choose changes with clear boundaries, tradeoffs, and recovery paths.

    by levnikolaevich · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • plan-review

    Multi-perspective plan review with VP Product, VP Engineering, and VP Design for implementation plans and architecture proposals.

    by wrsmith108 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • product-discovery-suite

    Decide what is worth building, who it serves, and what a useful first version must do.

    by levnikolaevich · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a similar job

  • mosaic

    DCVE methodology for systematic project planning, and Discuss for multi-perspective debate and decision-making — both powered by Claude Code agent teams

    by factorshin · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes a similar job

  • adr-writer

    Interactive ADR (Architecture Decision Record) writing tool with PRD traceability. Facilitates architectural decisions through guided Q&A sessions.

    by haandol · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes a similar job

Its card, with similar plugins by marketplace

What each says it does

Effect

In its own words, on Docker MCP Catalog:

Tools and resources for writing Effect code in Typescript.

architecture

In its own words, on Community GitHub marketplaces:

Decides the engineering approach for an intent in an interactive session: investigates, proposes two or three genuinely different approaches with trade-offs, recommends, lets the user decide, and writes the decision doc. Not a task-by-task plan; use cut-it. Not a multi-perspective debate; use design-council. Not product intent; use product-intent. Not a typed implementation handoff; use tech-spec.

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

architecture

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 architecture 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: architecture · 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