Ext Ops Panel
Open dashboard
Comparison

GitHub vs Sunstone Weave: Local Semantic Code Search

GitHub is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). 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-17. 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
MarketplaceGitHubSunstone Weave: Local Semantic Code Search
Official MCP Registry Listed
Version: 0.2.0
Downloads/month (npm): 216
Downloads/week (npm): 37
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
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

GitHub vs Sunstone Weave: Local Semantic Code Search
FactGitHubSunstone 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 (@abhishekmcp/github)On your machine (blackwindow-weave-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 11, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/abhishekkumar2021/mcp-suitegithub.com/space-bacon/blackwindow-weave-mcp
Changes in the last 7 days (differs)40
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

GitHub

In its own words, on Official MCP Registry:

GitHub via MCP: search, repos, issues, PRs, files, notifications. OAuth device flow or token.

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

GitHub As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio github -- npx -y @abhishekmcp/github

Requires: GITHUB_TOKEN (secret)

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 GitHub asks for

  • GITHUB_CLIENT_ID
  • GITHUB_READONLY
  • GITHUB_TOKEN (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: GitHub · What it can do: Sunstone Weave: Local Semantic Code Search · Compare two other plugins

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