Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • The install package comes from a different repo than this listing's
Own this project? Claim it
One Search MCP logo

One Search MCP

Searches the web, discovers URLs, scrapes pages, and prepares content through configurable providers and a local Chromium browser.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install One Search MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "one-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agent-browser"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y agent-browser

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

The one-search-mcp MCP server connects AI agents to web search providers and browser-based page operations. It exposes tools for searching, link discovery, scraping, and preprocessing text, with local search available without an API key. Browser-backed tools use agent-browser and require a Chromium-based browser, while search providers can be selected through environment variables. Reach for it when an agent needs to find web sources, inspect pages, collect links, or prepare multiple URLs for downstream analysis.

Use cases

  • Search the web with a selected provider
  • Discover links from a starting page
  • Scrape pages into Markdown or HTML
  • Capture full-page screenshots
  • Prepare text from multiple URLs

Key features

  • Multi-provider web search
  • Local browser search without API keys
  • URL discovery from page HTML
  • Configurable page scraping and browser actions
  • Multi-URL text preprocessing
  • Docker image with Chromium included

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · agent-browser (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars146Stargazers on the source repository.
npm downloads7.1MPackage downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How One Search MCP works

What one-search-mcp does

The one-search-mcp MCP server gives an MCP client a set of web research and page-processing tools. It can query a configured search provider, load a starting page and collect links, scrape selected page representations, and preprocess text from multiple URLs.

Search can use local browser automation or configured services including SearXNG, DuckDuckGo, Bing, Tavily, Google, Zhipu, Exa, Bocha, and You.com. The local provider uses a browser rather than an API key. Browser operations are handled locally through agent-browser, replacing the Firecrawl integration used by earlier releases.

How it works

The one_search tool returns results from the provider selected by SEARCH_PROVIDER. The default is local; other providers may require an API key, an API URL, or both. Local search supports browser-based searches through engines such as Bing, Google, Baidu, and Sogou.

one_map opens a starting URL in the browser and extracts links from its HTML. It accepts a URL, an optional search value, an includeSubdomains option, and a result limit. It discovers page links rather than operating as a sitemap crawler.

one_scrape loads one page and captures the formats requested by the caller. Available formats include Markdown, HTML, raw HTML, links, and screenshots, including full-page screenshots. Optional actions such as waiting, clicking, writing, pressing keys, and scrolling run in order before capture. JavaScript execution is available only when allowExecuteJavascript is explicitly enabled, and action processing stops at the first error.

one_extract accepts a list of URLs and returns preprocessed text blocks for later tools or models. It does not perform built-in LLM extraction.

Setup and configuration

Install the package with npx -y one-search-mcp or install it globally with npm. It can also run in Docker; the published images include Chromium. Claude Code, Claude Desktop, Cursor, and Windsurf configuration examples are provided by the project.

A Chromium-based browser is required for local search and browser-backed tools. The server can detect Chrome, Edge, Chromium, and Chrome Canary. If none is installed, Chromium can be installed through npx agent-browser install or by installing a browser separately.

Set SEARCH_PROVIDER to choose a search backend. SEARCH_API_KEY is needed for Tavily, Bing, Google, Zhipu, Exa, and Bocha; Google also uses SEARCH_API_URL for its Custom Search Engine ID. SearXNG uses SEARCH_API_URL, and You.com uses YDC_API_KEY. The local and DuckDuckGo providers do not require keys.

Tools and capabilities

The one-search-mcp MCP server exposes four tools:

  • one_search queries the selected search provider.
  • one_map finds links on a starting page.
  • one_scrape captures page content, links, screenshots, and supported browser-driven interactions.
  • one_extract prepares text from multiple URLs.

The MCP Inspector can be used to test the TypeScript or built server entrypoint during local development.

Limitations and notes

Browser-backed operations block private, loopback, and link-local targets by default. Set ALLOW_PRIVATE_NETWORK=true only in a trusted deployment when access to those targets is needed; the project warns that untrusted inputs or prompt injection could otherwise cause internal services to be fetched.

Several older fields are no longer accepted. one_map rejects removed sitemap-related fields, while one_scrape rejects fields such as onlyMainContent, extract, and location. Calls that use executeJavascript must also set allowExecuteJavascript to true. The Firecrawl environment variables are obsolete and should be removed when migrating from version 1.1.0 or earlier.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about One Search MCP

one-search-mcp is an MCP server that connects AI agents to web search providers and a local Chromium browser. Its main tools are one_search for search results, one_map for link discovery, one_scrape for page capture, and one_extract for preprocessing text from multiple URLs.

Install it with `npx -y one-search-mcp` or `npm install -g one-search-mcp`. Browser-backed features also require Chrome, Edge, Chromium, or Chrome Canary, while the Docker images include Chromium.

Yes, one-search-mcp works with Cursor through its `mcp.json` configuration.

It supports SearXNG, DuckDuckGo, Bing, Tavily, Google, Zhipu, Exa, Bocha, You.com, and local browser search. API keys or provider-specific settings are required for several hosted services, while local and DuckDuckGo search need no key.

Set `ALLOW_PRIVATE_NETWORK=true` to permit browser-backed tools to access private, loopback, and link-local targets. Use this only in trusted deployments because untrusted inputs or prompt injection could cause internal services to be fetched.

Related MCP servers

All in Search & Data Extraction All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOne Search MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/one-search-mcp?style=directory)](https://allmcps.com/mcp/one-search-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/one-search-mcp"><img src="https://allmcps.com/api/badge/one-search-mcp?style=directory" alt="One Search MCP on AllMCPs" /></a>