@semidark/mcp-litellm-searxng

MCP server for searching the web through a LiteLLM proxy's SearXNG-backed search endpoint.

Installation

No local installation required — the server is executed on-demand via npx:

{
  "mcp": {
    "azurelit-search": {
      "type": "local",
      "command": ["npx", "-y", "@semidark/mcp-litellm-searxng"],
      "environment": {
        "LITELLM_SEARCH_URL": "https://your-litellm-proxy/v1/search/searxng-search",
        "LITELLM_API_KEY": "sk-your-key",
        "LITELLM_TIMEOUT_MS": "30000"
      }
    }
  }
}

With OpenCode, you can usually reuse your existing secret file:

{
  "mcp": {
    "azurelit-search": {
      "type": "local",
      "command": ["npx", "-y", "@semidark/mcp-litellm-searxng"],
      "environment": {
        "LITELLM_SEARCH_URL": "https://litellm-proxy.example.com/v1/search/searxng-search",
        "LITELLM_API_KEY": "{file:~/.secrets/azure-lit.key}",
        "LITELLM_TIMEOUT_MS": "30000"
      }
    }
  }
}

Related MCP server: mcp-searxng

Development

Run the server locally:

npm start

Run the integration test harness:

LITELLM_SEARCH_URL="https://your-litellm-proxy/v1/search/searxng-search" \
LITELLM_API_KEY="sk-your-key" \
npm test

npm test is an integration test against a real LiteLLM endpoint. It does not mock the network and fails fast if LITELLM_SEARCH_URL or LITELLM_API_KEY is missing.

Environment Variables

Tools

web_search

Search the web using the configured LiteLLM proxy search backend.

Parameters:

• query (string, required): Search query

• max_results (number, optional, default 10): Max results to return (1–50)

Returns:

• text output formatted for chat clients

• structuredContent.results as the raw LiteLLM result array

License

MIT