🚀 OneSearch MCP Server: Web Search & Crawl & Scraper & Extract

@yokingma

About 🚀 OneSearch MCP Server: Web Search & Crawl & Scraper & Extract

🚀 OneSearch MCP Server: Web Search & Scraper & Extract, Support agent-browser, SearXNG, Tavily, DuckDuckGo, Bing, etc.

#mcp-server #modelcontextprotocol #searxng-mcp #tavily-mcp #duckduckgo-mcp #bing-mcp #firecrawl-mcp

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "one-search-mcp"
      ],
      "env": {
        "SEARCH_PROVIDER": "searxng",
        "SEARCH_API_URL": "http://127.0.0.1:8080",
        "SEARCH_API_KEY": "YOUR_API_KEY",
        "FIRECRAWL_API_URL": "http://127.0.0.1:3002",
        "FIRECRAWL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Tools

Search and retrieve content from web pages. Returns SERP results by default (url, title, description).

Scrape a single webpage and return markdown, HTML, links, or a screenshot. Supports navigation timeout, TLS verification control, full-page screenshots, bounded pre-scrape actions, and advanced executeJavascript only when allowExecuteJavascript is true.

Discover URLs from a starting point by loading a page in the browser and extracting links from its HTML.

Fetch and preprocess page content from one or more URLs. Returns cleaned text blocks that can be passed to downstream tools or models.

Overview

What is OneSearch MCP Server?

A Model Context Protocol (MCP) server that integrates with multiple search providers for web search, local browser search, URL discovery, and scraping capabilities using agent-browser. It is designed for developers building AI agents that need to search and extract web content via MCP tools.

How to use OneSearch MCP Server?

Install via npm (npx -y one-search-mcp) or Docker, then configure the search provider and optional API keys via environment variables. Use the exposed tools (one_search, one_scrape, one_map, one_extract) from any MCP client.

Key features of OneSearch MCP Server

Supports multiple search engines: SearXNG, Tavily, DuckDuckGo, Bing, Google, Zhipu, Exa, Bocha, and local browser search.
Local browser-based search (free, no API keys) using agent-browser with automatic Chromium detection.
Tools include: one_search, one_scrape, one_map, and one_extract.
Docker image with pre-installed Chromium for zero-setup deployment.
one_scrape supports multiple output formats: markdown, HTML, rawHtml, links, screenshot, full-page screenshot.

Use cases of OneSearch MCP Server

Perform web searches from an AI agent using a variety of providers with or without API keys.
Scrape a single page and return content in markdown, HTML, or screenshot format with optional pre-scrape actions.
Discover all URLs from a starting page (link discovery) via one_map.
Preprocess content from multiple URLs into clean text blocks for downstream LLM analysis.

FAQ from OneSearch MCP Server

What search providers are supported?

The server supports searxng, duckduckgo, bing, tavily, google, zhipu, exa, bocha, and local (browser-based). Default is local.

Do I need an API key?

It depends on the provider: local and duckduckgo require no API key; searxng requires a self-hosted URL; bing, tavily, google, zhipu, exa, and bocha require an API key.

What browsers are required for local search?

A Chromium-based browser (Google Chrome, Microsoft Edge, Chromium, or Google Chrome Canary) is required. The server auto‑detects installed browsers; otherwise, you can install Chromium via npx agent-browser install.

Can I run OneSearch MCP Server in Docker?

Yes. Docker images are available from GitHub Container Registry and Docker Hub, with Chromium pre‑installed. See the configuration example for Claude Desktop.

How do I migrate from v1.1.0 or earlier?

Remove Firecrawl environment variables, install a Chromium browser, and update to the latest version with npm install -g one-search-mcp@latest. Firecrawl has been replaced by agent-browser for local operations.

Frequently asked questions

What search providers are supported?

The server supports `searxng`, `duckduckgo`, `bing`, `tavily`, `google`, `zhipu`, `exa`, `bocha`, and `local` (browser-based). Default is `local`.

Do I need an API key?

It depends on the provider: `local` and `duckduckgo` require no API key; `searxng` requires a self-hosted URL; `bing`, `tavily`, `google`, `zhipu`, `exa`, and `bocha` require an API key.

What browsers are required for local search?

Can I run OneSearch MCP Server in Docker?

Yes. Docker images are available from GitHub Container Registry and Docker Hub, with Chromium pre‑installed. See the configuration example for Claude Desktop.

How do I migrate from v1.1.0 or earlier?

Remove Firecrawl environment variables, install a Chromium browser, and update to the latest version with `npm install -g one-search-mcp@latest`. Firecrawl has been replaced by agent-browser for local operations.

Comments

Basic information

More Search MCP servers

Ransack

chancewalker165-dot

Search and research for AI agents with source-attributed answers. Every result carries its source URL; unreadable pages are reported, not guessed.

Everything Search MCP Server

mamertofabian

344

G-Search MCP

jae-jae

A powerful MCP server for Google search that enables parallel searching with multiple keywords simultaneously.

268

Google Search Console MCP server for SEOs

AminForou

Google Search Console Insights with Claude AI for SEOs

1.1K

Brave Search MCP Server

mikechao

An MCP Server implementation that integrates the Brave Search API, providing, Web Search, Local Points of Interest Search, Image Search, Video Search, News Search and LLM Context Search capabilities

121