Open WebSearch

Fit and risk

Setup

{
  "mcpServers": {
    "web-search": {
      "command": "npx",
      "args": [
        "open-websearch@latest"
      ],
      "env": {
        "MODE": "stdio",
        "DEFAULT_SEARCH_ENGINE": "duckduckgo",
        "ALLOWED_SEARCH_ENGINES": "duckduckgo,bing,exa"
      }
    }
  }
}

{
  "servers": {
    "web-search": {
      "command": "npx",
      "args": [
        "open-websearch@latest"
      ],
      "env": {
        "MODE": "stdio",
        "DEFAULT_SEARCH_ENGINE": "duckduckgo",
        "ALLOWED_SEARCH_ENGINES": "duckduckgo,bing,exa"
      }
    }
  }
}

claude mcp add web-search -e MODE=stdio -e DEFAULT_SEARCH_ENGINE=duckduckgo -e ALLOWED_SEARCH_ENGINES=duckduckgo,bing,exa -- npx open-websearch@latest

Check that it works

After starting the server, the client tool list should show the six tools including search, fetchGithubReadme, and fetchWebContent; running a simple search query that returns structured results with titles and URLs confirms the install works.

Troubleshooting

1. Check environment variables (e.g., `DEFAULT_SEARCH_ENGINE`, `USE_PROXY`, `PORT`) are set correctly.
2. For streamable-http, ensure `baseUrl` points to `http://localhost:3000/mcp`.
3. If encountering network restrictions, set `USE_PROXY=true` and `PROXY_URL`.
4. If fetching certain sites fails, try Playwright mode (`SEARCH_MODE=auto`).

Things to try

Once connected, you can ask your AI assistant things like:

• Search for 'open-websearch MCP' with duckduckgo and return the top 3 resultsCopy
• Search 'Node.js performance tuning' across bing, csdn, and exa enginesCopy
• Fetch the README content of https://github.com/Aas-ee/open-webSearchCopy
• Retrieve the full text of the Juejin article https://juejin.cn/post/7520959840199360563Copy

Tools 6

No matching tools

Use cases

Supported clients

Listed from the project's documentation, not tested by this site.

Overview

Similar servers