Ext Ops Panel
Open dashboard
Comparison

rex vs Sunstone Weave: Local Semantic Code Search

rex is a plugin bundle for AI coding tools published by vykhovanets. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Sunstone Weave: Local Semantic Code Search is an MCP server published by space-bacon. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplacerexSunstone Weave: Local Semantic Code Search
Claude Code: claude-plugins-community Listed
Version: 0.1.12
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 703
Downloads/week (npm): 112
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

rex vs Sunstone Weave: Local Semantic Code Search
FactrexSunstone Weave: Local Semantic Code Search
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (rex-index)On your machine (blackwindow-weave-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/vykhovanets/rexgithub.com/space-bacon/blackwindow-weave-mcp
Changes in the last 7 days00
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

rex

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

Rex provides sub-second Python symbol search across all installed .venv packages. Three tools — rex_find, rex_show, rex_members — let Claude look up function signatures, docstrings, class members, and file locations instantly, without web search or grepping through source files. Results are grounded in the actually installed version — no outdated docs, no hallucinated parameters. Auto-indexes on first use and re-indexes incrementally when packages change. Read-only by design.

Sunstone Weave: Local Semantic Code Search

In its own words, on Official MCP Registry:

Semantic search over local folders of code and docs, with a code-search encoder running on your CPU.

How to run each

rex As a Claude Code plugin

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

Sunstone Weave: Local Semantic Code Search As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio blackwindow-weave-mcp -- npx -y blackwindow-weave-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 rex publish no settings it asks for, so we do not compare settings.

What it can do: rex · What it can do: Sunstone Weave: Local Semantic Code Search · 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. 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