Improve local service checks and web search tooling

This commit is contained in:
William Valentin
2026-02-22 22:12:44 -08:00
parent b477705806
commit f27aabae3b
12 changed files with 228 additions and 11 deletions
+9 -1
View File
@@ -459,6 +459,7 @@ SearXNG configuration:
web_search:
provider: searxng
endpoint: "http://searxng:8080"
fallback_endpoint: "https://searxng.homelab.local" # Optional backup endpoint
max_results: 5
```
@@ -466,7 +467,8 @@ web_search:
|-------|----------|-------------|
| `provider` | no | `brave` or `searxng` (default: `brave`) |
| `api_key` | yes (Brave) | Brave Search API key |
| `endpoint` | yes (SearXNG) | Base URL for self-hosted SearXNG |
| `endpoint` | yes (SearXNG primary) | Primary base URL for self-hosted SearXNG |
| `fallback_endpoint` | no (SearXNG) | Backup SearXNG base URL used if primary endpoint fails |
| `max_results` | no | Default result count for `web.search*` tools (default: `5`, max: `20`) |
Brave-specific query fields (supported by `web.search`, and by `web.search.news` except `safeSearch`):
@@ -482,6 +484,12 @@ Optional local Brave Search container (for MCP-based workflows):
docker compose --profile search up -d brave-search
```
Optional local SearXNG container (for self-hosted web search):
```bash
docker compose --profile search up -d searxng
```
Note: Flynn's built-in `web.search*` tools call Brave's HTTP API directly and use `web_search.api_key`; they do not route through the `brave-search` MCP container.
### Text-to-Speech (TTS) Reply Audio