serp-it
An MCP server that aggregates web search results from multiple engines and optionally renders pages to Markdown, providing a unified search interface.
README
serp-it
serp-it is an MCP (Model Context Protocol) server that exposes web search and optional page rendering capabilities through a simple stdio interface.
Features
- 🔍 Multi-Engine Search: Aggregates results from 7 search engines (AOL, Brave, Bing, DuckDuckGo, Yahoo, Startpage, Yandex)
- 📄 PDF Support: Automatically detects and extracts text from PDF documents
- 🌐 Page Rendering: Converts web pages to Markdown using headless Chromium
- ♻️ Browser Pooling: Efficient browser instance management for better performance
- 🗺️ Region Support: Search with locale/region codes (e.g., en-US, en-GB)
- 🔄 Result Deduplication: Merges duplicate results across engines
- 📦 Docker Ready: Includes Dockerfile for deployment with supergateway
AOL Search Integration
The AOL search engine often flies under the radar but returns unique SERP blends that combine Yahoo ranking signals with syndicated content. serp-it includes first-class AOL support with the following behavior:
- Requests are issued against
https://search.aol.com/aol/searchwith JavaScript disabled (nojs=1) so that results are stable for scraping. - Region hints are translated into
Accept-Languageheaders (en_US->en-US), giving you localized snippets where AOL supports them. - Result URLs are unwrapped with the same redirect decoder used for Yahoo, ensuring clean, direct links instead of AOL's tracking intermediaries.
- Duplicate links within the same result set are filtered before they reach the aggregator, protecting downstream clients from redundant entries.
If AOL should be temporarily disabled (for example during rate limiting) you can comment it out in src/SearchAggregator.ts and the rest of the stack will continue operating.
Supported Engines
| Engine | File | Notes |
|---|---|---|
| AOL | src/engines/Aol.ts |
HTML response, Yahoo-style redirect cleanup. |
| Brave | src/engines/Brave.ts |
Rapid updates, privacy-focused snippets. |
| Bing | src/engines/Bing.ts |
Provides richer entity cards. |
| DuckDuckGo | src/engines/DuckDuckGo.ts |
No personalization, global focus. |
| Yahoo | src/engines/Yahoo.ts |
Often mirrors AOL but with different ordering. |
| Startpage | src/engines/Startpage.ts |
Google-backed privacy results. |
| Yandex | src/engines/Yandex.ts |
Strong non-English indexing. |
Installation
npm install
npm run build
Playwright Setup
# Install Chromium used by Playwright
npm run playwright:install
# (Linux/WSL) install required system libraries
npm run playwright:install-deps
Usage
Run as MCP Server (stdio)
npm start
The server exchanges JSON-RPC 2.0 messages over stdio.
Tools
search: Aggregate results from the configured engines.search_fetch: Search and render the top matches to Markdown.
Inputs:
query(required string): Search query text.region(optional string): Locale code such asen-USorfr-FR.maxFetch(optional number,search_fetchonly): Number of rendered pages (default 5, max 10).
Outputs:
- Array of enriched search results (title, URL, snippet, engine metadata).
- Separate error lists for engine failures and fetch/render issues.
Development
# Rebuild on change
npm run dev
# Remove build artefacts
npm run clean
# Full clean build
npm run rebuild
# Run the integration tests
npm test
Docker Deployment
With supergateway
docker build -t serp-it-mcp .
docker run -p 8080:8080 serp-it-mcp
The container image bundles the MCP server alongside supergateway to expose SSE/HTTP endpoints on port 8080.
Environment Variables
PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH: Override the Chromium binary path.PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: Set to1to reuse a preinstalled browser.
Configuration
Claude Desktop (direct stdio)
Add the server to claude_desktop_config.json when running it locally via node:
{
"mcpServers": {
"serp-it": {
"command": "node",
"args": ["/path/to/serp-it/dist/index.js"]
}
}
}
Claude Desktop (Docker + supergateway SSE)
When you run the provided container (or start-gateway.sh), supergateway exposes an SSE bridge at http://localhost:8080/sse. Point Claude Desktop at that endpoint by updating claude_desktop_config.json:
{
"mcpServers": {
"serp-it-docker": {
"type": "sse",
"url": "http://localhost:8080/sse"
}
}
}
Adjust the host/port if you map the container differently. You can also add a headers object inside the block if your gateway requires authentication.
Claude Desktop (spawn with npx)
You can let Claude Desktop launch the server through npx, which downloads (or reuses) the published package on demand:
{
"mcpServers": {
"serp-it": {
"command": "npx",
"args": ["-y", "serp-it"]
}
}
}
If you are working from a clone of this repository, run npm run build first so that the serp-it binary points at dist/index.js.
Generic MCP Client (TypeScript)
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';
const transport = new StdioClientTransport({
command: 'node',
args: ['./dist/index.js']
});
const client = new Client({
name: 'my-client',
version: '1.0.0'
}, {
capabilities: {}
});
await client.connect(transport);
Project Structure
src/index.ts: Entry point for the MCP server.src/SearchAggregator.ts: Orchestrates engines and deduplication.src/PageRenderer.ts: Manages Playwright rendering and Markdown conversion.src/PdfParser.ts: Converts downloaded PDFs into text.src/BrowserPool.ts: Pools Chromium instances.src/ISearchEngine.ts: Interface definition for search engines.src/SearchResult.ts: Result data structure shared across engines.src/EngineUtils.ts: Shared scraping helpers.src/engines/Aol.ts: AOL search implementation.src/engines/Brave.ts: Brave search implementation.src/engines/Bing.ts: Bing search implementation.src/engines/DuckDuckGo.ts: DuckDuckGo search implementation.src/engines/Yahoo.ts: Yahoo search implementation.src/engines/Startpage.ts: Startpage search implementation.src/engines/Yandex.ts: Yandex search implementation.
License
ISC
Repository
https://github.com/luka-dev/serp-it
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
