[!NOTE]
sourceweave-search-mcp is the default local entrypoint. When explicit SOURCEWEAVE_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.
When no endpoint env vars are set, sourceweave-search-mcp:
Mode
What happens
Managed stack found
Join the existing SourceWeave-managed stack for the current runtime state directory
Healthy external stack found
Reuse the canonical local ports 19080, 19235, and 16379 without ownership
No reusable stack
Start and supervise a Docker-backed stack on canonical or free local ports
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.
Explicit endpoint mode
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 runs the tool directly. Use it when the supporting services are already available or when you provide explicit endpoints. It does not start Docker.
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.
Runtime configuration
Optional environment variables:
Variable
Purpose
SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL
SearXNG URL template. Must contain <query>.
SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL
Crawl4AI base URL.
SOURCEWEAVE_SEARCH_CACHE_REDIS_URL
Redis or Valkey URL used for caching.
FASTMCP_HOST
Host for sse or streamable-http transport.
FASTMCP_PORT
Port for sse or streamable-http transport.
If the endpoint variables are unset, sourceweave-search-mcp defaults to managed local runtime.
Canonical host endpoints remain the preferred defaults and the external-reuse probe targets.
A SourceWeave-managed stack may use different free host ports when the canonical defaults are already occupied.
Multiple MCP processes on the same machine share one managed stack per local runtime state directory.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich SourceWeave Web Search?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt SourceWeave Web Search einen API-Schlüssel?
Der Herausgeber nennt diese Umgebungsvariablen: SOURCEWEAVE_SEARCH_SEARXNG_BASE_URL, SOURCEWEAVE_SEARCH_CRAWL4AI_BASE_URL, SOURCEWEAVE_SEARCH_CACHE_REDIS_URL.
Welchen Transport verwendet SourceWeave Web Search?
SourceWeave Web Search läuft lokal über stdio.
Wann wurde SourceWeave Web Search zuletzt geprüft?
Zuletzt geprüft: 2026-11-09. Fully local MCP server and CLI for web research