Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
uvx sourceweave-web-search==0.5.0Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL=<value> SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL=<value> SOURCEWEAVE_SEARCH_CACHE_REDIS_URL=<value> claude mcp add io.github.mrnaqa-sourceweave-web-search -- uvx sourceweave-web-search==0.5.0Run in a terminal.
{ "mcpServers": { "io.github.mrnaqa-sourceweave-web-search": { "command": "uvx", "args": [ "sourceweave-web-search==0.5.0" ], "env": { "SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL": "<value>", "SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL": "<value>", "SOURCEWEAVE_SEARCH_CACHE_REDIS_URL": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
Search-first MCP server and CLI for web research.
[!NOTE]
sourceweave-search-mcpis the default local entrypoint. When explicitSOURCEWEAVE_SEARCH_*endpoint variables are absent, it discovers or starts the local Docker-backed stack automatically. If you already run the services yourself, set explicit endpoints and it will use them instead.
• • • • • • • •
Fully local MCP server and CLI for web research
SourceWeave Web Search gives MCP clients a compact three-tool contract for web research:
search_web(query, domains?, urls?, effort?) discovers sources and returns compact results with stable page_id handles.read_pages(page_ids, focus?) reads stored pages by page_id.read_urls(urls, focus?) reads direct URLs without searching first.It combines:
3.12+SOURCEWEAVE_SEARCH_* endpoints only if you want hosted or self-managed servicesRun the server from the published package:
uvx --from sourceweave-web-search sourceweave-search-mcp
Or start the MCP server over HTTP:
uvx --from sourceweave-web-search sourceweave-search-mcp \
--transport streamable-http \
--host 127.0.0.1 \
--port 8000
When no endpoint env vars are set, sourceweave-search-mcp:
Managed state lives under ~/.sourceweave-local/managed-runtime. Multiple MCP processes on the same machine share one managed stack per state directory.
[!IMPORTANT] Managed runtime removes containers only when the last active SourceWeave-managed process exits. Named volumes are preserved, so cache data survives restarts. If the original owning process dies, a later process can recover the same stack from Docker project identity and persisted runtime state.
If you already run SearXNG, Crawl4AI, and Redis or Valkey yourself, or want to point at hosted services, set explicit endpoints and the MCP entrypoint will bypass managed Docker startup:
SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL="http://127.0.0.1:19080/search?format=json&q=<query>" \
SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL="http://127.0.0.1:19235" \
SOURCEWEAVE_SEARCH_CACHE_REDIS_URL="redis://127.0.0.1:16379/2" \
uvx --from sourceweave-web-search sourceweave-search-mcp
sourceweave-search runs the tool directly. Use it when the supporting services are already available or when you provide explicit endpoints. It does not start Docker.
sourceweave-search --query "python programming" --read-first-pages 2
sourceweave-search --read-url "https://packaging.python.org/en/latest/"
[!TIP] The direct CLI also accepts
--searxng-base-url,--crawl4ai-base-url, and--cache-redis-urloverrides.
Example opencode.json / opencode.jsonc / ~/.config/opencode/opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sourceweave": {
"type": "local",
"command": [
"uvx",
"--from",
"sourceweave-web-search",
"sourceweave-search-mcp"
],
"enabled": true,
"timeout": 300000
}
}
}
For a shared HTTP endpoint instead:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sourceweave": {
"type": "remote",
"url": "http://127.0.0.1:18000/mcp",
"enabled": true,
"timeout": 300000
}
}
}
Example .vscode/mcp.json:
{
"servers": {
"sourceweave": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"sourceweave-web-search",
"sourceweave-search-mcp"
]
}
}
}
For a shared HTTP endpoint instead:
{
"servers": {
"sourceweave": {
"type": "http",
"url": "http://127.0.0.1:18000/mcp"
}
}
}
Example .mcp.json:
{
"mcpServers": {
"sourceweave": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"sourceweave-web-search",
"sourceweave-search-mcp"
]
}
}
}
For a project-scoped shared config, place the same block in .mcp.json at the repo root.
The direct CLI is useful once the supporting services are already reachable. It gives you the same search-first workflow without the MCP wrapper.
sourceweave-search --query "react useEffect cleanup example" --read-first-page
sourceweave-search --query "HTTP overview" --domain developer.mozilla.org --read-first-page
sourceweave-search --read-url "https://packaging.python.org/en/latest/"
The managed local runtime is for host-side uvx or uv run launches. Containerized deployments still use explicit endpoint wiring.
ghcr.io/mrnaqa/sourceweave-web-search-mcpdocker compose up -d --build mcpExample container run:
docker run --rm -p 8000:8000 \
-e SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL="http://host.docker.internal:19080/search?format=json&q=<query>" \
-e SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL="http://host.docker.internal:19235" \
-e SOURCEWEAVE_SEARCH_CACHE_REDIS_URL="redis://host.docker.internal:16379/2" \
ghcr.io/mrnaqa/sourceweave-web-search-mcp:latest
This repo also ships a generated standalone OpenWebUI tool file at artifacts/sourceweave_web_search.py.
From a repo checkout, verify it is in sync with the canonical implementation:
uv run sourceweave-build-openwebui --check
Paste that artifact into OpenWebUI when you want the standalone tool-file deployment path. The generated file rewrites the default endpoints to the repo-local compose service names so it matches the container deployment path out of the box.
Optional environment variables:
If the endpoint variables are unset, sourceweave-search-mcp defaults to managed local runtime.
Default endpoint values:
http://127.0.0.1:19080/search?format=json&q=<query>http://127.0.0.1:19235redis://127.0.0.1:16379/2Default preferred host ports for managed startup:
1908019235163798000 when run directly with uvx; 18000 at /mcp when using the repo's mcp compose servicegit clone https://github.com/MRNAQA/sourceweave-web-search.git
cd sourceweave-web-search
uv sync --locked --group dev
uv run sourceweave-search-mcp
Useful checks:
uv run sourceweave-build-openwebui --check
uv run sourceweave-search-mcp --help
uv run pytest tests/test_config.py tests/test_packaging.py tests/test_tool.py tests/test_managed_runtime.py -m "not integration"
© 2026 MCP Directory.
Fully local MCP server and CLI for web research
{ "mcpServers": { "io.github.mrnaqa-sourceweave-web-search": { "command": "uvx", "args": [ "sourceweave-web-search==0.5.0" ], "env": { "SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL": "<value>", "SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL": "<value>", "SOURCEWEAVE_SEARCH_CACHE_REDIS_URL": "<value>" } } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL, SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL, SOURCEWEAVE_SEARCH_CACHE_REDIS_URL.
SourceWeave Web Search runs locally over stdio.
Last checked 2026-11-09. Fully local MCP server and CLI for web research