OneSearch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARCH_API_KEY | No | The API key for the search provider. Required for 'tavily', 'bing', 'google', 'zhipu', 'exa', and 'bocha'. | |
| SEARCH_API_URL | No | The URL of the SearxNG API, or Google Custom Search Engine ID for 'google'. | |
| SEARCH_PROVIDER | No | The search provider to use. Supported: 'searxng', 'duckduckgo', 'bing', 'tavily', 'google', 'zhipu', 'exa', 'bocha', 'local'. Default is 'local'. | local |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| one_searchB | Search and retrieve content from web pages. Returns SERP results by default (url, title, description). |
| one_scrapeA | Scrape a single webpage and return markdown, HTML, links, or a screenshot. Supports navigation timeout, TLS verification control, full-page screenshots, bounded pre-scrape actions, and advanced executeJavascript only when allowExecuteJavascript is true. |
| one_mapA | Discover URLs from a starting point by loading a page in the browser and extracting links from its HTML. |
| one_extractA | Fetch and preprocess page content from one or more URLs. Returns cleaned text blocks that can be passed to downstream tools or models. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct core function: search returns SERP results, extract preprocesses multiple URLs, scrape handles single-page advanced operations, and map discovers links. There is minor overlap between extract and scrape for fetching page content, but their descriptions make the intended use cases clear.
All tool names follow the consistent pattern 'one_' prefix followed by a lowercase action verb (search, extract, scrape, map), with underscores between words. No mixed conventions or camelCase.
Four tools is well within the ideal range for a focused search/scraping server. Each tool covers a distinct aspect of web research, making the set feel appropriately scoped without being bloated.
The tool set covers the primary workflows: searching, extracting content, single-page scraping with advanced options, and link discovery. Minor gaps exist, such as no dedicated batch scraping tool, but the combined functionality handles most common use cases.