OneSearch

v1.2.1Search & Data Extractionstable

A Model Context Protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including SearXNG, Firecrawl, and Tavily.

agent-browserbing-mcpduckduckgo-mcpgoogle-search-mcpmcp-server
Share:
114
Stars
0
Downloads
0
Weekly
0/5

What is OneSearch?

OneSearch is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to model context protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including searxng, firecrawl, and tavily.

A Model Context Protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including SearXNG, Firecrawl, and Tavily.

This server falls under the Search & Data Extraction category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • one_search
  • one_extract
  • one_scrape
  • one_map

Use Cases

Execute web searches, scraping, crawling, and content extraction across engines.
Use Firecrawl for advanced web scraping and Tavily for LLM-optimized search.
Combine multiple search strategies (SearXNG, Bing, DuckDuckGo) in one tool.
yokingma

Maintainer

LicenseMIT License
Languagetypescript
Versionv1.2.1
UpdatedMay 11, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

NPM

npx -y one-search-mcp

Manual Installation

npx -y one-search-mcp

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use OneSearch

OneSearch MCP Server is a unified web search and scraping gateway for AI assistants that combines multiple search engines and scraping backends — SearXNG, DuckDuckGo, Bing, Google, Tavily, Firecrawl, Exa, and others — behind four consistent tools: one_search, one_scrape, one_map, and one_extract. It supports zero-key local search via DuckDuckGo or a self-hosted SearXNG instance as well as premium API-based providers, making it flexible for both local development and production AI agent deployments.

Prerequisites

  • Node.js 16 or higher and npm installed
  • A Chromium-based browser (Chrome, Edge, Chromium, or Chrome Canary) for local search and scraping features
  • An MCP-compatible client such as Claude Desktop, Cursor, or Cline
  • Optional: API keys for premium search providers (Tavily, Bing, Google, Firecrawl, Exa, etc.) depending on which provider you configure
1

Add the server via Claude Code CLI

The fastest way to add OneSearch is with the Claude Code CLI. This configures the server with default settings (local DuckDuckGo search, no API key required).

claude mcp add one-search-mcp -- npx -y one-search-mcp
2

Or configure manually in Claude Desktop

Edit your claude_desktop_config.json to add the server. With no environment variables set, it defaults to local search via DuckDuckGo.

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

Choose and configure a search provider

Set SEARCH_PROVIDER and any required keys for your preferred provider. Use 'duckduckgo' or 'local' for zero-API-key setups, or 'tavily', 'bing', 'google', etc. with their respective API keys.

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "npx",
      "args": ["-y", "one-search-mcp"],
      "env": {
        "SEARCH_PROVIDER": "tavily",
        "SEARCH_API_KEY": "YOUR_TAVILY_API_KEY"
      }
    }
  }
}
4

Configure SearXNG (self-hosted option)

If you run your own SearXNG instance, point OneSearch at it for private, no-key search.

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

Install agent-browser if local search fails

The local and DuckDuckGo providers use a headless browser. If Chrome is not auto-detected, install the bundled Chromium.

npx agent-browser install

OneSearch Examples

Client configuration (Tavily provider)

Claude Desktop configuration using Tavily as the search provider, which is optimized for LLM-friendly results.

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

Prompts to try

Example prompts exercising one_search, one_scrape, one_extract, and one_map capabilities.

- "Search the web for the latest news about large language models"
- "Scrape the content from https://example.com/article and summarize it"
- "Extract all links and headings from https://docs.example.com"
- "Search for 'best open source MCP servers 2025' and give me the top 5 results"
- "Crawl https://example.com and map all the pages you can find"
- "Search DuckDuckGo for Python async tutorials and fetch the top result"

Troubleshooting OneSearch

Local/DuckDuckGo search fails with 'browser not found'

OneSearch uses agent-browser for headless scraping. Run 'npx agent-browser install' to download a compatible Chromium binary, or ensure Chrome, Edge, or Chromium is installed and in your PATH. The tool auto-detects common install locations.

Tavily or Bing search returns 401 or 403 errors

Verify your SEARCH_API_KEY matches the provider set in SEARCH_PROVIDER. Each provider has its own API key from its own website (e.g., app.tavily.com for Tavily, Azure portal for Bing). Keys from one provider will not work with another.

SearXNG provider returns no results

Confirm your SEARCH_API_URL points to a running SearXNG instance (e.g., http://127.0.0.1:8080) and that the instance is configured to allow API/JSON queries. In your SearXNG settings, ensure 'search.formats' includes 'json'.

Frequently Asked Questions about OneSearch

What is OneSearch?

OneSearch is a Model Context Protocol (MCP) server that model context protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including searxng, firecrawl, and tavily. It connects AI assistants to external tools and data sources through a standardized interface.

How do I install OneSearch?

Install via npm with the command: npx -y one-search-mcp. Then add the server configuration to your AI client's JSON config file (e.g., claude_desktop_config.json or .cursor/mcp.json).

Which AI clients work with OneSearch?

OneSearch works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is OneSearch free to use?

Yes, OneSearch is open source and available under the MIT License license. You can use it freely in both personal and commercial projects.

Browse More Search & Data Extraction MCP Servers

Explore all search & data extraction servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "onesearch-mcp-server": { "command": "npx", "args": ["-y", "one-search-mcp"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use OneSearch?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides