Ext Ops Panel
Open dashboard
Comparison

workflow-builder vs FlowDot

workflow-builder is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). FlowDot is an MCP server published by flowdot.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceworkflow-builderFlowDot
Community marketplace alirezarezvani/claude-skills Listed
Version: 2.14.1
Forks (GitHub): 3 978
Stars (GitHub): 28 652
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.21
Downloads/month (npm): 904
Downloads/week (npm): 68
Forks (GitHub): 0
Stars (GitHub): 0
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

workflow-builder vs FlowDot
Factworkflow-builderFlowDot
Marketplaces that list it11
Stars (GitHub) (differs)28 652 (better)0 (worse)
Forks (GitHub) (differs)3 978 (better)0 (worse)
Last release (differs)2026-10-23Not published
Where it runs (differs)Installs as a plugin bundleOn your machine (@flowdot.ai/mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/alirezarezvani/claude-skillsgithub.com/flowdot-llc/mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-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

workflow-builder

In its own words, on Community GitHub marketplaces:

Workflow-builder skill: design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool (CLAUDE_CODE_WORKFLOWS=1, /workflows). Every session opens with an intake question set; when the user is vague, a stdlib recommendation engine infers and proposes a topology with rationale instead of stalling. Ships 3 stdlib Python tools (intake recommendation engine, .js validator enforcing pure-literal-meta / no-non-determinism / guarded-loop / parallel-thunk rules, topology scaffolder), 3 references citing 7-8 authoritative sources each (API surface, orchestration patterns, decision + intake guide), templates + a runnable example, cs-workflow-architect persona agent + /cs-workflow-build slash command. Use when building, scaffolding, or running a custom Claude Code workflow or orchestrating sub-agents (fan-out, pipeline, loop, judge-panel).

FlowDot

In its own words, on Official MCP Registry:

Build and run AI workflows, apps, toolkits and knowledge bases on FlowDot from any MCP client.

How to run each

workflow-builder As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install workflow-builder@claude-code-skills

FlowDot As a local MCP server: npm package

Claude Code
claude mcp add --env "FLOWDOT_API_TOKEN=<YOUR_FLOWDOT_API_TOKEN>" --transport stdio flowdot -- npx -y @flowdot.ai/mcp-server

Requires: FLOWDOT_API_TOKEN (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: workflow-builder · What it can do: FlowDot · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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