one-search-mcp

Overview

OneSearch MCP Server is a comprehensive web search and scraping tool that integrates with multiple search engines including SearXNG, Tavily, DuckDuckGo, Bing, and more. It features both API-based search and local browser automation through agent-browser, offering flexibility between free local operations and API-powered services. The server provides four main tools: one_search for web searching, one_scrape for content extraction, one_map for browser-based searches, and one_extract for content preprocessing. The implementation has recently transitioned from Firecrawl to agent-browser, improving privacy by handling browser operations locally without external API dependencies.

Try asking AI

After installing, here are 7 things you can ask your AI assistant:

• one_search

  Web search with multiple search engines

  Try:Search for the latest AI newsTry:Find information about climate change
• one_scrape

  Scrape content from web pages

  Try:Scrape the content of example.comTry:Extract data from this webpage
• one_map

  Map web content using browser automation

  Try:Map all links on this pageTry:Create a site map for example.com
• one_extract

  Preprocess multi-URL page content for analysis

  Try:Extract content from multiple URLsTry:Prepare scraped data for analysis

Comparable tools

Installation

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "npx",
      "args": ["-y", "one-search-mcp"],
      "env": {
        "SEARCH_PROVIDER": "local"
      }
    }
  }
}

# Install globally (Optional)
npm install -g one-search-mcp

# Or run directly with npx
npx -y one-search-mcp

# Pull the image
docker pull ghcr.io/yokingma/one-search-mcp:latest

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/yokingma/one-search-mcp:latest"],
      "env": {
        "SEARCH_PROVIDER": "local"
      }
    }
  }
}

FAQ

What browsers are supported by OneSearch MCP?

OneSearch MCP supports Chromium-based browsers including Google Chrome, Microsoft Edge, Chromium, and Google Chrome Canary. The server will automatically detect which browser is available.

Do I need API keys for all search providers?

No. Some providers like 'local' and 'duckduckgo' don't require API keys. Others like 'tavily', 'bing', 'google', 'zhipu', 'exa', and 'bocha' do require API keys.

How do I migrate from v1.1.0 or earlier?

Since v1.1.0 has removed Firecrawl integration, you need to install a Chromium browser and remove FIRECRAWL_API_URL and FIRECRAWL_API_KEY from your environment variables. Then update to the latest version.

Compare one-search-mcp with