
Semantic search over local folders of code and docs for any MCP client, with the Motherlode
Semantic search over local folders of code and docs for any MCP client, with the Motherlode code-search encoder running on your CPU.
·
Semantic search over the folders on your machine, for any MCP client. The server cuts source code and documentation into passages, embeds them with Motherlode, a 33M-parameter code-search encoder, on your CPU, and answers questions such as "where is a pairing line parsed into url, key and name" with file paths, line ranges and the passages themselves.
The only network requests are to huggingface.co on the first run: six requests, which leave five files, 133,752,819 bytes, in the cache. With the files cached, a run makes none.
This is the weave from Black Window and the Sunstone VS Code extension, packaged for clients that speak the Model Context Protocol. It runs on macOS, Linux and Windows with Node 20 or later.
Install it once from a terminal, before adding it to a client. This installs the package and ONNX Runtime and prints the version once the runtime has loaded:
npx -y [email protected] --versionOn GitHub's hosted runners, from an empty npm cache, this first install took 7 to 13 s on Linux and macOS and 55 to 69 s on Windows. Clients wait a limited time for a server to start (the MCP SDK's default is 60 s), and a client that stops waiting in the middle of an install can leave a broken copy in npm's cache (see Troubleshooting). Once installed, the server starts in under 3 s.
Keep the version in the client's configuration the same as here. With a version given, npx starts the copy it installed; with the bare name, npx (npm 11) looks for a newer version on every start and installs it while the client waits.
On Linux x64, ONNX Runtime also downloads 236 MB of CUDA libraries during the install. This server runs on the CPU and never loads them, so you can skip them:
ONNXRUNTIME_NODE_INSTALL=skip npx -y [email protected] --versionClaude Code:
claude mcp add weave -- npx -y [email protected] --folder /path/to/your/repoVS Code, in .vscode/mcp.json:
{
"servers": {
"weave": { "type": "stdio", "command": "npx", "args": ["-y", "[email protected]", "--folder", "${workspaceFolder}"] }
}
}Cursor, Claude Desktop, Windsurf and most other clients:
{
"mcpServers": {
"weave": { "command": "npx", "args": ["-y", "[email protected]", "--folder", "/path/to/your/repo"] }
}
}On Windows npx is a batch file, which a client can only start through cmd /c. Claude Code:
claude mcp add weave -- cmd /c npx -y [email protected] --folder C:\path\to\your\repoCursor, Claude Desktop, Windsurf and most other clients:
{
"mcpServers": {
"weave": { "command": "cmd", "args": ["/c", "npx", "-y", "[email protected]", "--folder", "C:/path/to/your/repo"] }
}
}In VS Code the same command and args go under servers in .vscode/mcp.json, with "type": "stdio".
npm install -g [email protected] installs a blackwindow-weave-mcp command, which a client can start
directly (cmd /c blackwindow-weave-mcp on Windows). To run from this repository instead of npm, replace
[email protected] in the arguments with github:space-bacon/blackwindow-weave-mcp.
| option | meaning |
|---|---|
--folder <path> | Weave this folder when the server starts. Repeatable. Optional: the model can call weave_folder itself. |
--cache <dir> | Where the encoder and the indexes live. Default ~/.cache/blackwindow-weave (on Windows %USERPROFILE%\.cache\blackwindow-weave), or BLACKWINDOW_WEAVE_CACHE. |
--version | Print the version and exit. |
Every push runs CI on Linux (x64 and arm64), Windows (x64) and macOS (Apple silicon),
each with Node 20, 22 and 24. Each job runs the stdio smoke test below from a checkout. It then installs the packed
package through npx from an empty npm cache, starts it the way a client does and weaves a folder. On Windows it also
starts it through cmd /c. Last, it installs the package globally and starts it by its command. Other platforms,
such as Windows on Arm, Intel Macs and Alpine Linux, are not tested.
The client times out when it first starts the server, or the server stops with Cannot find module ... transformers.node.mjs. A first install was interrupted, usually by a client that stopped waiting, and npm kept the
half-installed copy. Delete npm's npx cache and install again from a terminal with the line under Install:
rm -rf ~/.npm/_npxRemove-Item -Recurse -Force "$env:LOCALAPPDATA\npm-cache\_npx"Updating. Install the new version from a terminal as above, then change the version in the client's configuration.
| tool | what it does |
|---|---|
weave_folder | Index a folder, or bring its index up to date. Only files whose size or modification time changed are read again. A run longer than 25 s returns at once and continues in the background. |
weave_search | The passages nearest a plain-language or code query, with file, line range and score. Searches the folders woven in this session, or every woven folder if none was, or one folder when asked. |
weave_list | The woven folders with their file and passage counts, and any weave still running. |
weave_forget | Delete a folder's index. The folder's files are not touched. |
On an Apple M2 Ultra (24 CPU cores, Node 24.4.1), through the MCP SDK's own stdio client, in test/smoke.mjs:
| folder | files | passages | first weave | second weave | search |
|---|---|---|---|---|---|
this package's src/ | 6 | 42 | 3.8 s, with the encoder's download | 0.013 s | 5 to 6 ms |
| the Sunstone repository | 57 | 1,367 | 20.2 s | 0.014 s | 6 ms |
Embedding runs at about 68 passages a second on that machine, so a repository of 10,000 passages takes about two and a half minutes the first time. Those figures are one run each on one machine. The smoke test's three questions about this package's own source each return the expected file first; they are a check that the pieces are wired together, not a measure of retrieval quality. For retrieval quality see the model card.
.gitignore holds. Any other folder is walked, skipping
node_modules, build output, virtual environments, lock files and minified files. Files over 1 MB and files that
read as binary are skipped. JSON and XML are left out: in the Sunstone repository, result files under
bench/results/ took ranks 2 and 3 of the question above when they were included.onnx/model.onnx (fp32) through transformers.js and
ONNX Runtime on the CPU, CLS pooling.centring/mean_shipped.json) subtracted and is brought back
to unit length, so a score is a cosine after centring.<cache>/index/: a Float32 matrix and a JSONL of passages, named by a manifest that
is written to a temporary file and renamed into place, so an interrupted write leaves the previous index. An index
that cannot be read is moved aside rather than overwritten.Business Source License 1.1 with an internal-use grant. You may use it for any internal purpose, including commercial development on your own or your employer's code, with no limit on seats. You may not offer it to others as a hosted search service or ship it inside a product you supply. On 15 September 2030 it becomes Apache-2.0. The encoder is downloaded under its own licence, which has the same shape. For other terms, write to [email protected].
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add weave -- npx -y [email protected] --folder ${workspaceFolder}{
"mcpServers": {
"weave": {
"args": [
"-y",
"[email protected]",
"--folder",
"${workspaceFolder}"
],
"type": "stdio",
"command": "npx"
}
}
}code --add-mcp '{"name":"weave","args":["-y","[email protected]","--folder","${workspaceFolder}"],"type":"stdio","command":"npx"}'[mcp_servers.weave]
command = "npx"
args = ["-y", "[email protected]", "--folder", "${workspaceFolder}"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/blackwindow-weave-mcp to learn what the "Blackwindow Weave Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx -y [email protected] --versionclaude mcp add weave -- npx -y [email protected] --folder /path/to/your/repo
claude mcp add weave -- cmd /c npx -y [email protected] --folder C:\path\to\your\repoThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/blackwindow-weave-mcp)Nothing comparable is listed yet.
v0.1.20.1.2Release notesv0.1.10.1.1Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "blackwindow-weave-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.