Navigation
One Search MCP: Search & Extract Powerhouse - MCP Implementation

One Search MCP: Search & Extract Powerhouse

OneSearch MCP Server: Search, scrape, extract—all-in-one powerhouse. Unleash data potential, boost productivity, and streamline workflows effortlessly. 🚀

Research And Data
4.2(42 reviews)
63 saves
29 comments

Ranked in the top 9% of all AI tools in its category

About One Search MCP

What is One Search MCP: Search & Extract Powerhouse?

One Search MCP is a Model Context Protocol (MCP) server that unifies web search, scraping, crawling, and content extraction into a single workflow. By integrating tools like SearXNG, Firecrawl, and Tavily, it enables users to gather and process data from across the web efficiently.

How to Use One Search MCP: Search & Extract Powerhouse?

Getting started is straightforward:

  1. Install globally with npm install -g one-search-mcp or use npx.
  2. Set up environment variables for your chosen provider (e.g., SearXNG or Tavily).
  3. Configure your workspace in mcp.json or model_config.json with provider URLs and API keys.

Need help customizing settings? Check the deployment guide for advanced setups.

One Search MCP Features

Key Features of One Search MCP: Search & Extract Powerhouse?

  • Multi-tool integration: Switch between SearXNG, Firecrawl, Tavily, and more with minimal configuration.
  • Self-hosting support: Run core tools like SearXNG locally to control data privacy and costs.
  • Effortless scaling: Use environment variables to toggle providers or API keys without code changes.

Use Cases of One Search MCP: Search & Extract Powerhouse?

Businesses and developers use this tool for:

  • Automating market research by scraping product listings and pricing data
  • Building real-time news aggregators with customizable search pipelines
  • Powering chatbots with dynamic data from multiple web sources

One Search MCP FAQ

Frequently Asked Questions

Q: Does it work with my existing infrastructure?

A: Yes! Designed to plug into frameworks like Cursor or Windsurf, with full compatibility docs.

Q: How do I migrate from another scraping tool?

A: Import API keys and adjust provider settings in your config file – most setups take under 10 minutes.

Content

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

A Model Context Protocol (MCP) server implementation that integrates with Searxng/Firecrawl/Tavily for web search and scraping capabilities.

Features

  • Web Search, scrape, crawl and extract content from websites.
  • Support multiple search engines and web scrapers: SearXNG, Firecrawl, Tavily, etc.
  • Support for self-hosted: SearXNG, Firecrawl, etc. (see Deploy)
  • Enabled tools: one_search, one_scrape

Installation

# Manually install (Optional)
npm install -g one-search-mcp



# using npx
env SEARCH_API_URL=http://127.0.0.1:8080 FIRECRAWL_API_URL=http://127.0.0.1:3002 npx -y one-search-mcp

Environment Variables

Search:

  • SEARCH_PROVIDER (Optional): The search provider to use, either searxng or tavily, default is searxng.
  • SEARCH_API_URL (Optional): The URL of the SearxNG API, required for searxng.
  • SEARCH_API_KEY (Optional): The API key for the search provider, required for tavily.

Firecrawl:

  • FIRECRAWL_API_URL (Optional): The URL of the Firecrawl API, required for firecrawl.
  • FIRECRAWL_API_KEY (Optional): The API key for the Firecrawl API, required for firecrawl if using cloud service.

Running on Cursor

Your mcp.json file will look like this:

{
  "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"
      }
    }
  }
}

Running on Windsurf

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

{
  "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"
      }
    }
  }
}

Self-host

Local deployment of SearXNG and Firecrawl, please refer to Deploy

License

MIT License - see LICENSE file for details.

Related MCP Servers & Clients