Open WebSearch vs My Websearch

A side-by-side look at the Open WebSearch and My Websearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Open WebSearch logoOpen WebSearchSearch & Data Extraction · Local subprocess (stdio)Web search using free multi-engine search (NO API KEYS REQUIRED) — Supports Bing, Baidu, DuckDuckGo, Brave, Exa, and CSDN.69GreatAuth: no auth requiredMy Websearch logoMy WebsearchSearch & Data ExtractionMyWebSearch - multi-engine web search MCP server, CLI and local daemon. No API keys required.67GreatAuth: no auth required

Verdict: choose Open WebSearch for search & data extraction work as a local process; choose My Websearch for search & data extraction. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Open WebSearch logoChoose Open WebSearch when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search, fetchLinuxDoArticle, fetchCsdnArticle.
Explore Open WebSearch

My Websearch logoChoose My Websearch when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • Its auth model fits you: No auth required.
  • You want tools like search, fetchWebContent, fetchGithubContent.
Explore My Websearch

Feature & specification comparison

Rows where the two servers differ are marked.

SpecOpen WebSearch logoOpen WebSearchMy Websearch logoMy Websearch
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal69/100 · Great67/100 · Great
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,9003
Directory activity 14 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools64

Tools & capabilities

Open WebSearch tools 6

  • searchSearch the web using multiple engines (e.g., Baidu, Bing, DuckDuckGo, CSDN, Exa, Brave, Juejin(掘金), Startpage, Sogou(搜狗)) with no API key required. searchMode meanings: omit or set auto to use the server configured SEARCH_MODE; request forces request-based search; playwright forces browser-based search.
  • fetchLinuxDoArticleFetch full article content from a linux.do post URL
  • fetchCsdnArticleFetch full article content from a csdn post URL
  • fetchGithubReadmeFetch README content from a GitHub repository URL
  • fetchWebContentFetch content from a public HTTP(S) URL (supports Markdown files and normal web pages)
  • fetchJuejinArticleFetch full article content from a Juejin(掘金) post URL

My Websearch tools 4

  • searchSearch the web across multiple engines (Chinese/English/Code). Supports multi-query fan-out ('queries'), timeRange filtering, site limits, fetchTop article content, and no API keys required.
  • fetchWebContentFetch readable web content/docs/PDFs from public URLs. Auto-cleans ads, keeps code/tables. Batch urls (1-3), CSS selector scoping, bm25 focus, startIndex paging, cache, schema extract to JSON, citations, link retention.
  • fetchGithubContentFetch GitHub/Gitee by URL: README, source file (/blob/, with lines), tree, issue, PR, commit, compare, or releases. Example: https://github.com/o/r/blob/main/src/index.ts — ref can be branch/tag/commit; not a repo clone.
  • queryDocsGet official docs, API references, and code snippets for libraries/packages (e.g. 'react', 'fastapi', 'next.js'). Queries Context7 with fallback to npm/PyPI registry and GitHub README. Direct, no proxy needed.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Open WebSearch

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "aas-ee-open-websearch": {
      "command": "npx",
      "args": [
        "-y",
        "open-websearch@latest"
      ]
    }
  }
}

My Websearch

No confirmed install command for My Websearch yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Open WebSearch is categorized under Search & Data Extraction and uses a local stdio subprocess. My Websearch belongs to Search & Data Extraction and uses an install path we have not confirmed yet. Pick Open WebSearch for search & data extraction work and My Websearch for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. My Websearch has no confirmed install command yet — follow its own setup instructions.

Open WebSearch is listed as free. Auth: no auth required. My Websearch is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add aas-ee-open-websearch and my-websearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Open WebSearch has a quality signal of 69/100 (Great) with 14 views, 0 installs and 1,900 GitHub stars. My Websearch has 67/100 (Great) with 7 views, 0 installs and 3 GitHub stars.