What is the key difference between Open WebSearch and Webfetch?

Open WebSearch belongs to the Search & Data Extraction category with local stdio execution, while Webfetch belongs to the Search & Data Extraction category with local stdio execution.

How do I install Open WebSearch or Webfetch in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Open WebSearch and Webfetch free or paid?

Open WebSearch operates under a Free / Open Source model (No auth required). Webfetch operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Open WebSearch lists 6 tools with 2 views and 1,689 GitHub stars. Webfetch lists 6 tools with 2 views and 3 GitHub stars.

Can I use both Open WebSearch and Webfetch together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Open WebSearch or Webfetch in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Open WebSearch and Webfetch free to use, or do they require API keys?

Open WebSearch is listed under a Free / Open Source model with No auth required . Webfetch operates under a Freemium model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Open WebSearch and Webfetch at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both aas-ee-open-websearch and ashlrai-webfetch as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Open WebSearch has a Quality Score of 55 /100 ( Good ) with 2 views, 0 installs, and 1,689 GitHub stars. Webfetch holds a Quality Score of 51 /100 ( Good ) with 2 views, 0 installs, and 3 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Open WebSearch vs Webfetch

In-depth architectural comparison of the Open WebSearch and Webfetch MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Open WebSearch

Search & Data Extraction · Local stdio

Quality: 55/100 (Good) | Auth: No auth required

Webfetch

Search & Data Extraction · Local stdio

Quality: 51/100 (Good) | Auth: API Key required

Verdict Summary: Choose Open WebSearch if you need specialized Search & Data Extraction tools running via a local process. Choose Webfetch if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Open WebSearch when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: USE_PROXY, PROXY_URL.
Primary tools included: Multi-engine web search: Bing, Baidu, DuckDuckGo, Brave, Exa, CSDN, and others, No API keys or authentication required, Structured search results with titles, URLs, and descriptions.

Explore Open WebSearch Details

Choose Webfetch when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: UNSPLASH_ACCESS_KEY, PEXELS_API_KEY, PIXABAY_API_KEY, SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, BRAVE_API_KEY, BING_API_KEY, SERPAPI_KEY.

Feature & Specification Comparison

Specification	Open WebSearch Aas-ee Search & Data Extraction	Webfetch ashlrai Search & Data Extraction
Summary	Web search using free multi-engine search (NO API KEYS REQUIRED) — Supports Bing, Baidu, DuckDuckGo, Brave, Exa, and CSDN.	License-first federated image search across 25 providers. Returns open/platform/editorial license tags, attribution strings, dimensions, and download-ready URLs via npx -y getwebfetch-mcp.
Category & Scope	Search & Data Extraction

Tools & Capabilities Breakdown

Open WebSearch Tools (6)

Multi-engine web search: Bing, Baidu, DuckDuckGo, Brave, Exa, CSDN, and others

No API keys or authentication required

Structured search results with titles, URLs, and descriptions

Configurable default search engine and number of results

Support for HTTP proxy configuration

Content fetching from CSDN, GitHub READMEs, and generic web/Markdown pages

Webfetch Tools (6)

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Open WebSearch Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aas-ee-open-websearch": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ],
      "env": {
        "USE_PROXY": "YOUR_USE_PROXY_HERE",
        "PROXY_URL": "YOUR_PROXY_URL_HERE"
      }
    }
  }
}

Webfetch Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ashlrai-webfetch": {
      "command": "npx",
      "args": [
        "-y",
        "getwebfetch-mcp"
      ],
      "env": {
        "UNSPLASH_ACCESS_KEY": "YOUR_UNSPLASH_ACCESS_KEY_HERE",
        "PEXELS_API_KEY": "YOUR_PEXELS_API_KEY_HERE",
        "PIXABAY_API_KEY": "YOUR_PIXABAY_API_KEY_HERE",
        "SPOTIFY_CLIENT_ID": "YOUR_SPOTIFY_CLIENT_ID_HERE",
        "SPOTIFY_CLIENT_SECRET": "YOUR_SPOTIFY_CLIENT_SECRET_HERE",
        "BRAVE_API_KEY": "YOUR_BRAVE_API_KEY_HERE",
        "BING_API_KEY": "YOUR_BING_API_KEY_HERE",
        "SERPAPI_KEY": "YOUR_SERPAPI_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Open WebSearch is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Webfetch belongs to Search & Data Extraction using local stdio subprocess. Select Open WebSearch when you need capabilities focused on search & data extraction and Webfetch when you require tools for search & data extraction.

More alternatives to Open WebSearch More alternatives to Webfetch Search & Data Extraction category hub