Ext Ops Panel
Open dashboard
Comparison

craft vs io.github.lennix1337/genexus

craft is a plugin bundle for AI coding tools published by Darin Drobinski. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.lennix1337/genexus is an MCP server published by lennix1337. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. 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
Marketplacecraftio.github.lennix1337/genexus
Community marketplace drobins25/craft Listed
Version: 2.11.0
Forks (GitHub): 7
Stars (GitHub): 69
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.4
Downloads/month (npm): 7 136
Downloads/week (npm): 600
Forks (GitHub): 27
Stars (GitHub): 37
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.16.0
Downloads/month (npm): 7 136
Downloads/week (npm): 600
Forks (GitHub): 27
Stars (GitHub): 37
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

craft vs io.github.lennix1337/genexus
Factcraftio.github.lennix1337/genexus
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)69 (better)37 (worse)
Forks (GitHub) (differs)7 (worse)27 (better)
Last release (differs)2026-10-19 (better)2026-10-17 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (genexus-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)12Not published
Parts of the bundle (differs)82Not a bundle
LicenceMITMIT
Repository (differs)github.com/drobins25/craftgithub.com/lennix1337/genexus18mcp
Changes in the last 7 days (differs)52
First seen (differs)2026-10-162026-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

craft

In its own words, on Community GitHub marketplaces:

A Claude Code plugin that acts as an intelligent harness for your development workflow: your codebase is read-only by default, every change passes through a Write Gate as planned and approved work, and craft tracks your project's history, design tokens, and decisions locally so Claude learns your taste and architectural preferences over time.

io.github.lennix1337/genexus

In its own words, on Official MCP Registry:

Read, edit, and analyze GeneXus 18 KB objects from Claude, Cursor, and AI agents.

How to run each

craft As a Claude Code plugin

Claude Code
/plugin marketplace add drobins25/craft
/plugin install craft@craft

io.github.lennix1337/genexus As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio genexus -- npx -y genexus-mcp

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: craft · What it can do: io.github.lennix1337/genexus · 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. Package data comes from the public npm registry (registry.npmjs.org). 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