Ext Ops Panel
Open dashboard
Comparison

Workflow Engine vs io.github.shofer-dev/slang-workflows

Workflow Engine is a plugin bundle for AI coding tools published by AxGord. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.shofer-dev/slang-workflows is an MCP server published by shofer-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 Engineio.github.shofer-dev/slang-workflows
Claude Code: claude-plugins-community Listed
Version: 0.1.11
Forks (GitHub): 2
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 127
Downloads/week (npm): 20
Forks (GitHub): 0
Stars (GitHub): 1
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 Engine vs io.github.shofer-dev/slang-workflows
FactWorkflow Engineio.github.shofer-dev/slang-workflows
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (slang-workflows)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITApache-2.0
Repository (differs)github.com/axgord/claude-workflowgithub.com/shofer-dev/claude-code-slang-orchestrator
Changes in the last 7 days (differs)04
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

Workflow Engine

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

A Claude Code plugin that drives agents through YAML-defined state machines. Define workflows as YAML with states, transitions, and prompts. The engine tracks state, enforces guards, manages nested sub-workflow stacks, and persists every mutation atomically. Includes 16 bundled workflows covering the full agent lifecycle — from task routing and coding to review, testing, and reflection. Ships with a web dashboard for real-time session monitoring and workflow graph visualization.

io.github.shofer-dev/slang-workflows

In its own words, on Official MCP Registry:

Provable, declarative multi-agent workflows for Claude Code (typed .slang, non-LLM executor).

How to run each

Workflow Engine As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-workflow@claude-community

io.github.shofer-dev/slang-workflows As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio slang-workflows -- npx -y slang-workflows

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

Neither one's marketplaces publish the settings it asks for.

What it can do: Workflow Engine · What it can do: io.github.shofer-dev/slang-workflows · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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