one-search-mcp
Health Pass
- License Γ’β¬β License: MIT
- Description Γ’β¬β Repository has a description
- Active repo Γ’β¬β Last push 0 days ago
- Community trust Γ’β¬β 101 GitHub stars
Code Fail
- fs module Γ’β¬β File system access in package.json
- process.env Γ’β¬β Environment variable access in src/index.ts
- exec() Γ’β¬β Shell command execution in src/libs/agent-browser/index.ts
Permissions Pass
- Permissions Γ’β¬β No dangerous permissions requested
This MCP server acts as a unified gateway for web searching, scraping, crawling, and data extraction. It routes queries through multiple configurable search providers (like DuckDuckGo, Bing, and Tavily) or uses a local Chromium-based browser for automation.
Security Assessment
The overall risk is rated as Medium. The tool naturally makes extensive outbound network requests to fetch search results and scrape websites. It accesses environment variables (`process.env`), which is a standard practice for loading user API keys and search provider configurations, though you should avoid placing hardcoded secrets in your environment without care.
The most notable security flag is the tool's use of shell command execution (`exec()`) and file system access. This behavior is directly tied to its `agent-browser` dependency, which automates a local Chromium instance. While necessary for the tool's scraping features, executing shell commands always introduces an elevated risk. If inputs are not perfectly sanitized, it could potentially expose the host system to command injection vulnerabilities.
Quality Assessment
The project demonstrates strong health indicators. It is licensed under the permissive and standard MIT license. Maintained actively, the repository saw updates as recently as today. It has garnered over 100 GitHub stars, suggesting a reasonable level of community trust and adoption for an open-source utility.
Verdict
Use with caution β while actively maintained and licensed under MIT, the inherent security risks of local browser automation and shell execution require you to run it in a controlled, trusted environment.
π OneSearch MCP Server: Web Search & Scraper & Extract, Support agent-browser, SearXNG, Tavily, DuckDuckGo, Bing, etc.
π OneSearch MCP Server: Web Search & Crawl & Scraper & Extract
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 extract 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-browserfor browser automation. - Free, no API keys required.
- Use
- 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_URLandFIRECRAWL_API_KEYare no longer used.
What Changed:
one_scrapeandone_mapnow useagent-browserinstead of Firecrawlone_extracttool is now fully implemented for structured data extraction from multiple URLs- 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_URLandFIRECRAWL_API_KEYfrom 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:
# 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 islocal. - 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:
- Google Chrome: https://www.google.com/chrome/
- Microsoft Edge: https://www.microsoft.com/edge
- Chromium: https://www.chromium.org/getting-involved/download-chromium/
Or install via agent-browser:
npx agent-browser install
License
MIT License - see LICENSE file for details.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found