Release v1.2.0 - Add Configurable Engines and STDIO Mode
🚀 New Features
Configurable Search Engines
- New Environment Variable:
ALLOWED_SEARCH_ENGINES
- Restrict available search engines by specifying comma-separated engine names
- Provides better control over which engines can be used in your deployment
- If the default engine is not in the allowed list, the first allowed engine becomes the default
- Example:
ALLOWED_SEARCH_ENGINES=duckduckgo,bing,exa
Mode Switching Parameters
- Enhanced MODE Configuration:
MODE environment variable now supports three options:
stdio - STDIO mode only (ideal for MCP client integration)http - HTTP server mode only (for web-based access)both - Both STDIO and HTTP modes (default behavior)
- Flexible Deployment: Choose the most appropriate mode for your use case
📋 Configuration Reference
| Variable |
Default |
Options |
Description |
ALLOWED_SEARCH_ENGINES |
empty (all available) |
Comma-separated engine names |
Limit which search engines can be used |
MODE |
both |
both, http, stdio |
Server operation mode |
🔧 Usage Examples
Restricted Engine Usage
# Linux/macOS
ALLOWED_SEARCH_ENGINES=duckduckgo,bing DEFAULT_SEARCH_ENGINE=duckduckgo npx open-websearch@latest
# Windows PowerShell
$env:ALLOWED_SEARCH_ENGINES="duckduckgo,bing"; $env:DEFAULT_SEARCH_ENGINE="duckduckgo"; npx open-websearch@latest
Mode-specific Deployments
# STDIO only (for MCP clients)
MODE=stdio npx open-websearch@latest
# HTTP only (for web access)
MODE=http npx open-websearch@latest
# Windows CMD STDIO mode
set MODE=stdio && set DEFAULT_SEARCH_ENGINE=duckduckgo && npx open-websearch@latest
