CRW Web Scraper vs OpenBrand
A side-by-side look at the CRW Web Scraper and OpenBrand MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CRW Web Scraper for search & data extraction work as a local process; choose OpenBrand 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 CRW Web Scraper 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:
CRW_API_KEY, CRW_NO_AGENTS.
Choose OpenBrand when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENBRAND_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 53/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CRW_API_KEYCRW_NO_AGENTS | OPENBRAND_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,172 | 801 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View CRW Web Scraper | View OpenBrand |
Tools & capabilities
CRW Web Scraper tools
No tool names declared yet. Check the project README from the listing page.
OpenBrand tools
No tool names declared yet. Check the project README from the listing page.
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.
CRW Web Scraper
{
"mcpServers": {
"crw-web-scraper": {
"command": "npx",
"args": [
"-y",
"crw-mcp@latest"
],
"env": {
"CRW_API_KEY": "YOUR_CRW_API_KEY_HERE",
"CRW_NO_AGENTS": "YOUR_CRW_NO_AGENTS_HERE"
}
}
}
}
OpenBrand
{
"mcpServers": {
"openbrand": {
"command": "npx",
"args": [
"-y",
"openbrand-mcp"
],
"env": {
"OPENBRAND_API_KEY": "YOUR_OPENBRAND_API_KEY_HERE"
}
}
}
}
Frequently asked questions
CRW Web Scraper is categorized under Search & Data Extraction and uses a local stdio subprocess. OpenBrand belongs to Search & Data Extraction and uses a local stdio subprocess. Pick CRW Web Scraper for search & data extraction work and OpenBrand 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.
CRW Web Scraper has no declared pricing — check the project's own site. Auth: api key required. OpenBrand has no declared pricing — check the project's own site. 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 crw-web-scraper and openbrand as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CRW Web Scraper has a quality signal of 53/100 (Good) with 1 views, 0 installs and 1,172 GitHub stars. OpenBrand has 47/100 (Fair) with 1 views, 0 installs and 801 GitHub stars.