Ext Ops Panel
Open dashboard
Comparison

walkeros vs Weavatrix

walkeros is a plugin bundle for AI coding tools published by elbwalker. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Weavatrix is an MCP server published by Weavatrix. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplacewalkerosWeavatrix
Community marketplace elbwalker/walkeros Listed
Version: 0.2.0
Forks (GitHub): 23
Stars (GitHub): 347
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.17.5
Downloads/month (npm): 3 890
Downloads/week (npm): 406
Forks (GitHub): 0
Stars (GitHub): 4
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

walkeros vs Weavatrix
FactwalkerosWeavatrix
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)347 (better)4 (worse)
Forks (GitHub) (differs)23 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@walkeros/mcp)On your machine (weavatrix)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)232
LicenceMITMIT
Repository (differs)github.com/elbwalker/walkerosgithub.com/weavatrix/weavatrix
Changes in the last 7 days22
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

walkeros

In its own words, on Community GitHub marketplaces:

Skills and MCP tools for walkerOS - build sources, destinations, transformers, and flows.

Weavatrix

In its own words, on Official MCP Registry:

Native Weavatrix MCP: 67 read-only tools for code, local CI, n8n, Dify, agents, Mermaid, Web3.

How to run each

walkeros As a Claude Code plugin

Claude Code
/plugin marketplace add elbwalker/walkeros
/plugin install walkeros@elbwalker

Weavatrix As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio weavatrix -- npx -y weavatrix 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

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

What it can do: walkeros · What it can do: Weavatrix · 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