Hey👋, I built something I think you’ll dig:
🔗 GitHub: https://github.com/Aas-ee/open-webSearch
🐳 Docker: ghcr.io/aas-ee/open-web-search:latest
✨ What It Does
- Supports Bing, Baidu, CSDN (linux.do in progress)
- ZERO API keys—no quotas, no login
- Returns structured JSON:
{title, url, description, source, engine}
- Fully MCP-compatible: streamableHttp & SSE transport styles
- Built-in article scraping:
fetchCsdnArticle
,fetchLinuxDoArticle
- One-command Docker deploy for self-hosting
🧪 Example in Action
1. Start the server
git clone https://github.com/Aas-ee/open-webSearch
cd open-webSearch
npm install && npm run build
node build/index.js
or via Docker:
docker run -d -p 3000:3000 ghcr.io/aas-ee/open-web-search:latest
2. Add to your MCP client config
Streamable HTTP version (e.g., Claude Dev / Cherry Studio):
"mcpServers": {
"web-search": {
"type": "streamableHttp",
"url": "http://localhost:3000/mcp"
}
}
SSE alternative:
"mcpServers": {
"web-search": {
"type": "sse",
"url": "http://localhost:3000/sse"
}
}
3. Use it in a tool call
use_mcp_tool({
server_name: "web-search",
tool_name: "search",
arguments: {
query: "Claude plugin tutorial",
limit: 3,
engines: ["bing", "csdn"]
}
})
➡️ Returns structured results:
[
{
"title": "How to write a Claude plugin",
"url": "...",
"description": "...",
"source": "CSDN",
"engine": "csdn"
}
]
And to fetch a full article:
use_mcp_tool({
server_name: "web-search",
tool_name: "fetchCsdnArticle",
arguments: {
url: "https://blog.csdn.net/.../details/..."
}
})
✅ Why It Matters
- 💸 No API keys, no costs
- 🔎 Multi-engine = richer, broader results
- 🧠 Plug-and-play for Claude, LangChain, RAG systems
- 🏗️ Great for real-time Q&A, smart agents, prompt-enhanced workflows
What’s Next?
- Google, Reddit, YouTube engine support
- Poll: which engine/source do you want next?
If you try it, I’d love feedback, issues/PRs, or just a ⭐️. Let me know how it fits in your MCP workflow! 🙏
Top comments (0)