/ Directory / Playground / Open WebSearch MCP
● Community Aas-ee ⚡ Instant

Open WebSearch MCP

by Aas-ee · Aas-ee/open-webSearch

Multi-engine search behind one MCP — fall back across Google, Bing, DuckDuckGo, and Brave when one rate-limits.

Open WebSearch aggregates several search engines under one MCP. Automatic fallback handles rate limits. Useful when a single engine isn't reliable enough for your agent.

Why use it

Key features

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "open-web-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "open-websearch"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "open-web-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "open-websearch"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "open-web-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "open-websearch"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "open-web-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "open-websearch"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "open-web-search-mcp",
      "command": "npx",
      "args": [
        "-y",
        "open-websearch"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "open-web-search-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "open-websearch"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add open-web-search-mcp -- npx -y open-websearch

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Open WebSearch MCP

Research with engine fallback

👤 Developers ⏱ ~15 min intermediate

When to use: Your research agent gets rate-limited on a single engine.

Flow
  1. Search
    search query="..." engines=auto.✓ Copied
    → Results from whichever engine responds
  2. Iterate
    Filter by date, re-search.✓ Copied
    → Tight result set

Outcome: No single-engine bottleneck for research workflows.

Combinations

Pair with other MCPs for X10 leverage

open-web-search-mcp + firecrawl

Search here, deep-crawl with Firecrawl

Combine open-web-search-mcp with firecrawl: Search here, deep-crawl with Firecrawl✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
search (see docs) Multi-engine search 1 call
fetch (see docs) Pull a result page as markdown 1 call

Cost & Limits

What this costs to run

API quota
Per-engine free tiers
Tokens per call
Snippets small; pages large
Monetary
Free (engines have ToS)
Tip
Respect engine ToS; don't hammer a single one

Security

Permissions, secrets, blast radius

Credential storage: None
Data egress: Configured engines
Never grant: scrape with hostile UA strings

Troubleshooting

Common errors and fixes

All engines rate-limit

Wait and retry; or add an API-key engine like Brave Search API

Alternatives

Open WebSearch MCP vs others

AlternativeWhen to use it insteadTradeoff
exa-mcpYou want LLM-tuned searchPaid above free tier

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills