Ext Ops Panel
Open dashboard
Comparison

avicenna vs Sunstone Weave: Local Semantic Code Search

avicenna is a plugin bundle for AI coding tools published by smrf1093. 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-27. 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
MarketplaceavicennaSunstone Weave: Local Semantic Code Search
Claude Code: claude-plugins-community Listed
Version: 0.1.0
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): 718
Downloads/week (npm): 35
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

avicenna vs Sunstone Weave: Local Semantic Code Search
FactavicennaSunstone Weave: Local Semantic Code Search
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (blackwindow-weave-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/smrf1093/avicennagithub.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

avicenna

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

Code knowledge graph MCP extension — semantic code search, symbol lookup, and dependency analysis powered by tree-sitter and vector embeddings

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

avicenna As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install avicenna@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

Only avicenna asks for

  • HUGGINGFACE_TOKENIZER (secret)

Only Sunstone Weave: Local Semantic Code Search asks for

  • BLACKWINDOW_WEAVE_CACHE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

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