What is the key difference between Open WebSearch and Open Sales Stack?

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

How do I install Open WebSearch or Open Sales Stack 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 Open Sales Stack free or paid?

Open WebSearch operates under a Free / Open Source model (No auth required). Open Sales Stack operates under a BYOK (Pay Provider Direct) 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. Open Sales Stack lists 5 tools with 2 views and 2 GitHub stars.

Can I use both Open WebSearch and Open Sales Stack 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 Open Sales Stack 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 Open Sales Stack free to use, or do they require API keys?

Open WebSearch is listed under a Free / Open Source model with No auth required . Open Sales Stack operates under a BYOK (Pay Provider Direct) 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 Open Sales Stack at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both aas-ee-open-websearch and ekas-io-open-sales-stack 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. Open Sales Stack holds a Quality Score of 44 /100 ( Fair ) with 2 views, 0 installs, and 2 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Open WebSearch vs Open Sales Stack

In-depth architectural comparison of the Open WebSearch and Open Sales Stack 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

Open Sales Stack

Search & Data Extraction · Local stdio

Quality: 44/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Open WebSearch if you need specialized Search & Data Extraction tools running via a local process. Choose Open Sales Stack 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 Open Sales Stack 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 (BYOK (Pay Provider Direct)).
You have access to required keys: LLM_PROVIDER, OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_GEMINI_API_KEY.

Feature & Specification Comparison

Specification	Open WebSearch Aas-ee Search & Data Extraction	Open Sales Stack ekas-io Search & Data Extraction
Summary	Web search using free multi-engine search (NO API KEYS REQUIRED) — Supports Bing, Baidu, DuckDuckGo, Brave, Exa, and CSDN.	Collection of B2B sales intelligence MCP servers. Includes website analysis, tech stack detection, hiring signals, review aggregation, ad tracking, social profiles, financial reporting and more for AI-powered prospecting by Ekas
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

Open Sales Stack Tools (5)

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"
      }
    }
  }
}

Open Sales Stack Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ekas-io-open-sales-stack": {
      "command": "npx",
      "args": [
        "-y",
        "ekas-io-open-sales-stack"
      ],
      "env": {
        "LLM_PROVIDER": "YOUR_LLM_PROVIDER_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "GOOGLE_GEMINI_API_KEY": "YOUR_GOOGLE_GEMINI_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Open WebSearch More alternatives to Open Sales Stack Search & Data Extraction category hub