Search1api MCP vs Crw
A side-by-side look at the Search1api MCP and Crw 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 Crw for search & data extraction as a local process. 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. - You want tools like
search, news, crawl.
Choose Crw when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
crw_scrape, crw_crawl, crw_check_crawl_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 67/100 · Great | 72/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | OAuth 2.0 |
| Pricing | Paid service | Freemium |
| Required env vars | SEARCH1API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 173 | 1,172 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 8 |
| Full listing | View Search1api MCP | View Crw |
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.
Crw tools 8
crw_scrapeScrape one URL to markdown, HTML, or links.crw_crawlStart an async site crawl; returns a job id to poll with crw_check_crawl_status.crw_check_crawl_statusPoll an async crawl job and retrieve its pages.crw_mapDiscover URLs on a site via sitemap and/or a short crawl. Returns a URL list only, no page content.crw_extractExtract structured JSON from URLs via a prompt and/or JSON schema. Async job — poll crw_check_extract_status with the returned id. Needs an LLM.crw_check_extract_statusPoll an extract job; returns status and, when complete, a per-URL results array.crw_cancel_extractRequest cancellation of an extract job. Returns the canonical status; cancelling remains non-terminal until the claimed URL settles.crw_parse_fileParse a local PDF (base64 in contentBase64) to markdown. No OCR: scanned PDFs return empty markdown with a warning.
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"
],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY_HERE"
}
}
}
}
Crw
{
"mcpServers": {
"us-crw": {
"command": "npx",
"args": [
"-y",
"crw-mcp@latest"
]
}
}
}
Frequently asked questions
Search1api MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Crw belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Search1api MCP for search & data extraction work and Crw 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.
Search1api MCP is listed as a paid service. Auth: api key required. Crw is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 us-crw 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 173 GitHub stars. Crw has 72/100 (Great) with 5 views, 0 installs and 1,172 GitHub stars.