A Model Context Protocol (MCP) server implementation that integrates with multiple search providers for web search, local browser search, URL discovery, and scraping capabilities with agent-browser.
Features
🚀 OneSearch MCP Server: Web Search & Scraper & Extract, Support agent-browser, SearXNG, Tavily, DuckDuckGo, Bing, etc.
Advanced pre-scrape action: executeJavascript. If actions contains executeJavascript, you must set allowExecuteJavascript: true.
actions run serially before content capture and fail fast on the first action error.
Removed fields such as onlyMainContent, extract, and location are rejected at the schema boundary.
one_extract
Accepts only urls and returns preprocessed text blocks for downstream tools or models.
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:
Install Chromium browser (see Prerequisites)
Remove FIRECRAWL_API_URL and FIRECRAWL_API_KEY from your environment variables
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:
# 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
Local Debugging with MCP Inspector
Use the official MCP Inspector to interactively test tools, resources, and prompts against this server during local development.
# Inspect the TypeScript source entrypoint
npm run inspector
# Inspect the built server entrypoint
npm run inspector:build
# Example with explicit environment variables
ALLOW_PRIVATE_NETWORK=true SEARCH_PROVIDER=local npm run inspector
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
ALLOW_PRIVATE_NETWORK (Optional): Set to true to allow browser-backed tools (one_scrape, one_map, one_extract) to access private, loopback, and link-local network targets. Defaults to false.
Use ALLOW_PRIVATE_NETWORK=true only in trusted deployments. When enabled, prompt injection or untrusted tool inputs can make the MCP process fetch internal services that are otherwise blocked by default.