My Websearch MCP server

MyWebSearch

🇨🇳 中文 | 🇺🇸 English

my-websearch provides an MCP server, CLI, and local daemon, and can also be paired with skill-guided agent workflows for live web search and content retrieval without API keys.

Features

• Web search using multi-engine results
• Domestic engines (no proxy needed): bing, baidu, csdn, juejin, sogou
• Overseas engines (⚠️ proxy required in mainland China): duckduckgo, exa, brave, startpage
• HTTP proxy configuration support for accessing restricted resources
• No API keys or authentication required
• Returns structured results with titles, URLs, and descriptions
• Configurable number of results per search
• Customizable default search engine
• Support for fetching individual article content
• csdn
• github (README files)
• generic HTTP(S) page / Markdown content

Choose the Right Path

• MCP
• Best when you want to connect my-websearch to Claude Desktop, Cherry Studio, Cursor, or another MCP client.
• CLI
• Best for one-shot local commands, shell scripts, and direct terminal usage.
• Local daemon
• Best when you want a reusable long-lived local HTTP service exposing status, GET /health, and POST /search / POST /fetch-*. Start it explicitly with my-websearch serve and check it with my-websearch status.
• Skill
• Best as an agent-facing guidance layer for setup and usage. A skill does not replace MCP, CLI, or the local daemon; it typically works together with the CLI and/or local daemon to help an agent discover, activate, and use the smallest working path.

Use with a Skill

Install the my-websearch skill for your agent first:

npx skills add https://gitee.com/wtznicy/my-websearch --skill my-websearch

On first use, the skill typically follows this path: detect whether a usable my-websearch path already exists, guide setup/enablement if it does not, validate that the capability is active, and only then continue with search or fetch through the smallest working path.

If the current environment cannot complete setup or activation automatically, you can explicitly have the agent start the local daemon first:

my-websearch serve
my-websearch status

Keep installation proxy settings separate from runtime proxy settings:

• Installation proxy / mirror
• Use this when the skill or agent is installing my-websearch, playwright, or other npm packages.
• In restricted networks, npm-specific flags or npm config often work better than generic shell proxy variables, for example:

npm --proxy http://127.0.0.1:7890 --https-proxy http://127.0.0.1:7890 install -g my-websearch

• Runtime proxy
• Use this when the daemon is already installed and is about to perform live search / fetch work.
• This affects the my-websearch network traffic after serve starts, for example:

USE_PROXY=true PROXY_URL=http://127.0.0.1:7890 my-websearch serve

If the agent can only get through the package-install step with npm proxy settings, but live search/fetch also needs a proxy after startup, those are two separate configuration steps and should be handled separately.

CLI and Local Daemon

CLI is for one-shot execution. The local daemon is a long-lived local HTTP service for repeated calls with lower startup friction. Use my-websearch serve as the explicit daemon start command and my-websearch status as the explicit daemon status command.

Shortened. The full README is on GitHub.