Search1api MCP vs My Websearch
A side-by-side look at the Search1api MCP and My Websearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Search1api MCP 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?
Choose Search1api MCP when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SEARCH1API_KEY, MCP_ALLOWED_HOSTS, MCP_ALLOWED_ORIGINS. - You want tools like
search, news, crawl.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 67/100 · Great | 67/100 · Great |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | SEARCH1API_KEYMCP_ALLOWED_HOSTSMCP_ALLOWED_ORIGINS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 174 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 5 | 4 |
| Full listing | View Search1api MCP | View My Websearch |
Tools & capabilities
Search1api MCP tools 5
searchSearch the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Pass a result URL to crawl to retrieve the full page.newsSearch current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.crawlExtract the readable title and full text from a public URL supplied by the user or returned by search.sitemapDiscover related public links from a page or domain when the user wants to explore a site's structure or available pages.trendingList currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.
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.
Search1api MCP
{
"mcpServers": {
"fatwang2-search1api-mcp": {
"command": "npx",
"args": [
"-y",
"search1api-mcp@latest"
],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY_HERE",
"MCP_ALLOWED_HOSTS": "YOUR_MCP_ALLOWED_HOSTS_HERE",
"MCP_ALLOWED_ORIGINS": "YOUR_MCP_ALLOWED_ORIGINS_HERE"
}
}
}
}
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
Search1api MCP 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 Search1api MCP 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.
Search1api MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 fatwang2-search1api-mcp and my-websearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Search1api MCP has a quality signal of 67/100 (Great) with 1 views, 0 installs and 174 GitHub stars. My Websearch has 67/100 (Great) with 7 views, 0 installs and 3 GitHub stars.