1. Conduid
  2. Browser
  3. One Search MCP
MCP server · Browser

One Search MCP

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

71Good

Scored 4 days ago · breakdown

About One Search MCP

One Search MCP is an MCP server published by yokingma in the Browser category: 🚀 OneSearch MCP Server: Web Search & Scraper & Extract, Support agent-browser, SearXNG, Tavily, DuckDuckGo, Bing, etc. It has been installed 0 times through Conduid.

The repository has 79 stars and 18 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx one-search-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about One Search MCP

Powered by Claude · Grounded in docs

I know everything about One Search MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v1.2.4Version 1.2.4 · 31 Jul 2026What's Changed feat: add optional you.com search provider by @mouse-value-add in https://github.com/yokingma/one-search-mcp/pull/13 fixed: DuckDuckGo safe-search mapping (`0=off`, `1=moderate`, `2=strict`). Fixes #11. Improved `one_scrape`…
v1.2.2Version 1.2.2 · 26 Jun 2026one-search-mcp v1.2.2 This release focuses on security hardening and MCP runtime updates. What's Changed Hardened browser-backed scraping against SSRF. Blocked private, loopback, link-local, and other non-public network targets by default.…
v1.2.1Version 1.2.1 · 16 Apr 2026Full Changelog**: https://github.com/yokingma/one-search-mcp/compare/v1.2.0...v1.2.1 fix(search): repair searxng provider requests
v1.2.0Version 1.2.0 · 8 Apr 2026Full Changelog**: https://github.com/yokingma/one-search-mcp/compare/v1.1.3...v1.2.0
v1.1.3Version 1.1.3 · 6 Apr 2026v1.1.3 This patch release focuses on cancellation safety, process cleanup, and release packaging. Highlights Fixed MCP request cancellation for browser-backed tools. Aborted requests now close active `AgentBrowser` instances immediately…

README

🚀 OneSearch MCP Server: Web Search & Crawl & Scraper & Content Prep

A Model Context Protocol (MCP) server implementation that integrates with multiple search providers for web search, local browser search, and scraping capabilities with agent-browser.

Features

  • Web search, scrape, crawl and preprocess content from websites.
  • Support multiple search engines and web scrapers: SearXNG, Tavily, DuckDuckGo, Bing, Google, Zhipu (智谱), Exa, Bocha (博查), etc.
  • Local web search (browser search), support multiple search engines: Bing, Google, Baidu, Sogou, etc.
    • Use agent-browser for browser automation.
    • Free, no API keys required.
  • Enabled tools: one_search, one_scrape, one_map, one_extract

Migration from v1.1.0 and Earlier

Breaking Changes in v1.1.0:

  • Firecrawl Removed: The Firecrawl integration has been removed in favor of agent-browser, which provides similar functionality without requiring external API services.
  • New Browser Requirement: You must install Chromium browser (see Prerequisites section).
  • Environment Variables: FIRECRAWL_API_URL and FIRECRAWL_API_KEY are no longer used.

What Changed:

  • one_scrape and one_map now use agent-browser instead of Firecrawl
  • one_extract now preprocesses multi-URL page content for downstream analysis instead of performing built-in LLM extraction
  • All browser-based operations are now handled locally, providing better privacy and no API costs

Migration Steps:

  1. Install Chromium browser (see Prerequisites)
  2. Remove FIRECRAWL_API_URL and FIRECRAWL_API_KEY from your environment variables
  3. Update to the latest version: npm install -g one-search-mcp@latest

Prerequisites

Browser Requirement: This server uses agent-browser for web scraping and local search, which requires a Chromium-based browser.

Good News: The server will automatically detect and use browsers already installed on your system:

  • ✅ Google Chrome
  • ✅ Microsoft Edge
  • ✅ Chromium
  • ✅ Google Chrome Canary

If you don't have any of these browsers installed, you can:

# Option 1: Install Google Chrome (Recommended)
# Download from: https://www.google.com/chrome/

# Option 2: Install Microsoft Edge
# Download from: https://www.microsoft.com/edge

# Option 3: Install Chromium via agent-browser
npx agent-browser install

# Option 4: Install Chromium directly
# Download from: https://www.chromium.org/getting-involved/download-chromium/

Installation

Using Claude Code CLI (Recommended)

# Add to Claude Code with default settings (local search)
claude mcp add one-search-mcp -- npx -y one-search-mcp

# Add with custom search provider (e.g., SearXNG)
claude mcp add one-search-mcp -e SEARCH_PROVIDER=searxng -e SEARCH_API_URL=http://127.0.0.1:8080 -- npx -y one-search-mcp

# Add with Tavily API
claude mcp add one-search-mcp -e SEARCH_PROVIDER=tavily -e SEARCH_API_KEY=your_api_key -- npx -y one-search-mcp

Manual Installation

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

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

Using Docker

Docker image includes all dependencies (Chromium browser) pre-installed, no additional setup required.

Pull the image:

# From GitHub Container Registry
docker pull ghcr.io/yokingma/one-search-mcp:latest

# Or from Docker Hub
docker pull zacma/one-search-mcp:latest

Configure with Claude Desktop:

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

With custom search provider:

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "SEARCH_PROVIDER=tavily",
        "-e", "SEARCH_API_KEY=your_api_key",
        "ghcr.io/yokingma/one-search-mcp:latest"
      ]
    }
  }
}

Environment Variables

Search Engine:

  • SEARCH_PROVIDER (Optional): The search provider to use, supports searxng, duckduckgo, bing, tavily, google, zhipu, exa, bocha, local, default is local.
  • SEARCH_API_URL (Optional): The URL of the SearxNG API, or Google Custom Search Engine ID for google.
  • SEARCH_API_KEY (Optional): The API key for the search provider, required for tavily, bing, google, zhipu, exa, bocha.
// supported search providers
export type SearchProvider = 'searxng' | 'duckduckgo' | 'bing' | 'tavily' | 'google' | 'zhipu' | 'exa' | 'bocha' | 'local';

Search Provider Configuration

Provider API Key Required API URL Required Notes
local No No Free, uses browser automation
duckduckgo No No Free, no API key needed
searxng Optional Yes Self-hosted meta search engine
bing Yes No Bing Search API
tavily Yes No Tavily API
google Yes Yes (Search Engine ID) Google Custom Search
zhipu Yes No 智谱 AI
exa Yes No Exa AI
bocha Yes No 博查 AI

Configuration for Other MCP Clients

Claude Desktop

Add to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Cursor

Add to your mcp.json file:

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

Windsurf

Add to your ./codeium/windsurf/model_config.json file:

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

Self-hosting SearXNG (Optional)

If you want to use SearXNG as your search provider, you can deploy it locally using Docker:

Prerequisites:

  • Docker installed and running (version 20.10.0 or higher)
  • At least 4GB of RAM available

Quick Start:

# Clone SearXNG Docker repository
git clone https://github.com/searxng/searxng-docker.git
cd searxng-docker

# Start SearXNG
docker compose up -d

After deployment, SearXNG will be available at http://127.0.0.1:8080 by default.

Configure OneSearch to use SearXNG:

# Set environment variables
export SEARCH_PROVIDER=searxng
export SEARCH_API_URL=http://127.0.0.1:8080

For more details, see the official SearXNG Docker documentation.

Troubleshooting

Browser not found error

If you see an error like "Browser not found", the server couldn't detect any installed Chromium-based browser. Please install one of the following:

Or install via agent-browser:

npx agent-browser install

License

MIT License - see LICENSE file for details.

README mirrored from the source repository 4 days ago. The original is authoritative.

Questions

About One Search MCP

How do I install One Search MCP?

Run npx one-search-mcp, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is One Search MCP safe to use with an AI agent?

Its trust score is 71 out of 100 (good). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is One Search MCP still maintained?

Yes — the latest release is v1.2.4 (31 Jul 2026), and the last commit was 7 months ago. The repository has 79 stars and 0 open issues.